Suppose you are charged with system QA for a complicated system that expects dozens or hundreds of simultaneous users. The system has a user front end through either a browswer of through deployed software, and it sends transactions back and … Continue reading →

For the past couple of months, most of my work has been in that last, most overlooked arc of the development life cycle: maintenance. Specifically, I’ve spent a lot of time diagnosing problems, tracking down their origins in the code, … Continue reading →