J. Ambrose Little

J. Ambrose Little

Ambrose currently works as the Codemunicator for Infragistics, the leader in presentation layer components. He's contributed to two books, Professional ADO.NET 2 and ASP.NET 2 MVP Hacks, both by Wrox, and he speaks at local events and conferences when he can. You can reach him via email or his blog at http://dotNetTemplar.Net .

Articles Authored

  • Purporting the Potence of Process

    Last updated: Tuesday, February 19, 2019

    Published in: CODE Magazine: 2007 - March/April

    Do you ever feel like you’re beating your head against a wall? I know I do; quite often, in fact. It seems like developers spend half of their time bending technology to their purposes when the technology doesn’t really quite fit. Well, I’m actually thinking of one problem in particular right now, namely that of validation. Can you think of a more boring topic? There are few, but I think you can agree that it is an extremely important one in business software.

  • I Object

    Last updated: Wednesday, February 20, 2019

    Published in: CODE Magazine: 2006 - January/February

    I Object

  • Am I a Mad Scientist?

    Last updated: Friday, December 26, 2025

    Published in: CODE Magazine: 2005 - May/June

    J. Ambrose Little argues that building an application around a strongly typed, rich domain model—rather than a database-centric or data-set approach—offers real, practical business benefits: easier maintenance, greater code reuse, improved performance, and faster, safer development thanks to compile-time checks and better tooling. He contends that object-oriented design decouples the domain from the database, reduces coupling to UI layers, and enables clearer, more dependable architectures, ultimately making development more enjoyable and less error-prone.

  • Sorting Custom Collections

    Last updated: Friday, December 26, 2025

    Published in: CODE Magazine: 2005 - January/February

    Have you ever wanted to use a strongly-typed collection to bind your data presentation controls to, only to find that you have very limited sorting capabilities, if any at all?If you are trying to stick to good object-oriented design and shrink the amount of data that you keep in memory, transfer from your data source, or serialize to clients, you likely have run into this situation because you are using strongly-typed collections of your domain objects. So what do you do if you need to sort those collections for presentation or faster searching?