In what ways should software be like a house? In a recent issue of STQE magazine, Technical Editor Brian Marick’s musings about the concept of “tinkerable software” generated some interesting discussion about the very nature of software design. This week’s column runs a portion of that piece so that our Sticky-minded readers can sink their thoughts into the concept.
Pete TerMaat shares some valuable lessons learned from a summer with "hacking legend" Richard Stallman. He learned that attitude, passion for one's work, was most important. Reviews, coding standards, porting guidelines, bug hunting advice, and other measures can fall flat without a passion for clean code, for "getting things right."
Johanna Rothman recommends the book Adaptive Software Development by James Highsmith. She says, "Highsmith shows the reader how to recognize when development practices need to change and how to acquire the skills to adapt. For a fresh approach to software development, be sure to check it out."
Do you have a bug database or defect tracking system? Whether you call them PRs, CRs, SPRs, or some other acronym, logging your software problems into a database rates as one of the simplest yet most effective things you can do to improve product quality. Sometimes these databases turn into the electronic equivalent of a “roach motel” trap--the bugs go in but they don’t come out!
Adaptive Software Development (ASD) is one of a growing number of alternatives to traditional, process-centric software management methods. Extreme Programming (XP), Lean Development, SCRUM, and Crystal Light methods—although different in many respects—are tied together by a focus on people, results, minimal methods, and maximum collaboration. They are geared to the high speed and high change of today's e-business projects.