techscapades

Maintenance programmers get a bad wrap. They're seen tucked away in the corner, frustrated, cleaning up others' bugs. Occasionally, they'll hack a new feature into old code, but without being there from the beginning, their code is usually clumsy. There's little chance to get in on a sexy new project building something cool.

In comes the scheduled maintenance programmer. The difference is in the problem they are presented. They're given a software product prior to it blowing up and challenged to make sure it's gonna keep running smoothly. Change the spark plugs, flush and fill, calipers and rotors -- whatever it takes.

The principles of XP/TDD teach us to refactor our own code to ensure the highest quality before ever delivering it, but technical debt inevitably slips through. Often we abstract more than necessary, creating unnecessary complexity. Other times we miss an abstraction, forcing duplicated code. The scheduled maintenance programmer's role is to remove that debt, run/write additional tests (and automate them where not already), refactor to improve maintainability, and keep the ship moving at full steam ahead.

I want to work in a shop where these guys are respected. Where they take a Porsche, tune it up, and make it run like a Ferrari.