April 23, 2004
The Ten Rules of Performance
Paul Vick has a nice discussion of why performance should be considered 1. in the design, 2. during coding, 3. during testing, 4. during fixing the bugs, and not only during the hectic chaos of final bugfixing in the week before the release. A definite must read for all programmers, both aspiring and experienced!
And since I'm pretty sure that there will be some who will react to the very first paragraph with a sarcastic laugh and a snide anti-Microsoft remark, allow me to remind you that some of the best books on software design - Writing Solid Code and Code Complete - have actually been written by Microsoft employees.
Via Tony Bowden.
Posted by roam at April 23, 2004 12:07 PM