I was listening to a Hanselminutes podcast and he mentioned a reference to the "Who Moved My Cheese" book (not sure if it was intentional!). It's a great little book about managing change in life and specifically at work. Well worth a read even if you think you are ok with handling change. Good stuff, it's a really small if you aren't normally a reader. I think I have already given my copy to someone but it's only a couple of quid so pick it up.
This happens regularly to me (and from my anecdotal investigation everyone involved in large / old projects). We need a new piece of functionality. I write it, it's beautiful and I win the internet. I have estimated 8 days (or 22.23 lol-points depending on how you live) and it's only taken 4 days. Ah, but then a very small; mostly ignored and very unimportant detail rears it's cruel head. You need to make it work with the code that exists already. This is normally in the form of saving to some pre-existing entities. Oh dear. You save everything through the various management / service classes that exist already and nothing works. So begins the next couple of days of horror. You find that you didn't set the work = true . Most of my woes in this area are caused by modifications at layer further down (or the stored procedure it finally ends up in) changing the object that I was trying to save or not saving part of the object because of some rule. So many errors
Comments