Gift Peddie's good post brings up a real sore spot with me... why does everyone think that the Agile Manifesto says "No
Documentation" whatsoever? Why does everyone think that if you document code (especially embedded documentation) that you're a sissy of some sort? Why does everyone think that having a simple implementation plan in black and white is somehow against the ability to move quickly?
IT managers of the world... wake up. Insist on proper embedded documentation so it never gets separated from the code and then give people time to do it right. Then insist on code reviews and make them part of everyone's job using pay reviews as enforcement. If you lose a couple of programmers because of it, good... they needed to be replaced anyway.
And remember... "If you want it real bad, you'll probably get it that way." ;-)
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is usually not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs