Tip #63, p328, The Pragmatic Programmer
And Tip #62 is equally as good, "Test Early. Test Often. Test Automatically."
Friday, October 22, 2010
Friday, October 15, 2010
Before debugging, fix warnings
"It doesn't make sense to waste time trying to find a problem that the compiler could find for you!" - The Pragmatic Programmer, p 92
Sharpen the saw daily, but if you spend all your time sharpening the saw, nothing will ever get cut.
Determine the amount of time you will spend on a sharpen the saw activity beforehand. You can't spend all of your time in kaizen, or what's the point of kaizen in the first place?
Have show and tell every week
Have something new to show to your stakeholders every week as you develop your project. This not only allows the stakeholders to feel good about the progress of the project, it also allows you to get feedback to make sure you're on course. It would be great if you could release every week, but that's not always possible. Do release regularly. But show a demo of new features you're working on, even if they're not complete.
Wednesday, October 13, 2010
Subscribe to:
Comments (Atom)