All code is not created equal. Learn from a master of the craft how to spot bad code and mold it into good. This month, Mike Clark explains how moving code from one class to another to make it reusable can save you time in the long run.

More and more software testing is becoming a technical activity—and that means programming. In the future, simply having domain knowledge won't be enough. Good craftspeople need good tools, and some of the most powerful tools in the tester’s toolbox today are dynamic programming languages like Perl and Ruby. If you aren't familiar with these languages, this article will help you get up to speed and start scripting in no time.

Examples of mistakes, manifestations, and problems help us understand all parts of the software. Brian Marick suggests Web resources that examine software failures.

It doesn't matter when you deliver, if you build the wrong product. Development entails inferences and assumptions about the user, which are supposed to guide the build-process. However, even if development successfully matches the inferences and assumptions about the user, if those criteria don't match the Real User, the product fails. This article talks about how to incorporate the user into the requirements and design phase.