posted @ Tuesday, January 9, 2007 2:11 PM
Jeremy Miller has an excellent read on writing orthogonal code. Do not pass go, do not collect $200 until you have read this post. If you have even more time (read: an hour at a minimum) I highly recommend reading Big Ball of Mud which dissolves the forces behind what cause software architectures to fail and discusses solutions to address them. Finally, Jason Yip hit the nail on the head when discusses what it takes for last minute changes to be safe. Several years ago I worked on a team that produced a calculation engine for life insurance policies. Our team had a process defined for implementing last minute change requests that required the approval of our IT director, and several times I saw those requests denied. While we did have support for many of the points Jason identifies, quality should not be sacrificed over a delivery schedule. DHH covers this in Chapter 5 of Getting Real - Build half a product, not a half-ass product. Thoughts?