Have you ever been hunting a bug and been absolutely sure that it was in someone else's code, only to find out that, nope, it was in yours all along? I sure did. Come along with me as we explore my latest minor failure and remind ourselves that, most of
We have this big project we're working on (which I have written [http://www.exceptionnotfound.net/between-two-stacks-the-consequences-of-a-data-less-decision/] about before [http://www.exceptionnotfound.net/entity-framework-and-wcf-loading-related-entities-with-automapper-and-reflection/] ) and one of the things we need to do on this project is automatic logging of changes made to model objects. I've worked out a way
We've been having an ongoing debate in our team about what archicture to use to implement our new enterprise-level application. There are two possible solutions, one familiar, one fast, but we can't seem to reach a conclusion as to which to use. A lack of applicable data is forcing us
> There are only two hard things [http://martinfowler.com/bliki/TwoHardThings.html] in Computer Science: cache invalidation and naming things. > -- Phil Karlton Naming things is hard. Image taken from [How to Name Things](http://slidedeck.io/hoontw/naming-things), used under [license](https://creativecommons.org/licenses/by/4.0/)As
I met a new team member (we'll call him Jerry) in our department today, and he offhandedly mentioned something that blew my mind. We're on the verge of a sea change in my organization, and only now am I becoming aware that the Agile process I thought I'd been doing