Throw Code Away

The third and final part of my agile architecture series.


Part one suggested walking skeletons for new features or projects. Part two suggested building the limited, smallest and simplest functionality possible. However you do not always have the luxury of deferral. Likewise if the project already exists and you are amending functionality, a walking skeleton is going to be limited.

Solution

Throw code away. This sounds brutal and overkill, but throwing code away has many advantages.

Benefits

Objections

Throwing code away should not be taken lightly, but it is certainly a valid technique under the right circumstances.

You will have an easier time suggesting to start over on two days worth of work than you would two weeks, two months or two years. Keep your batch sizes small and the ability to throw code away will become easier to accept, with the benefits outweighing the negatives.

Small batches are not the only prerequisite to suggest throwing code away. Small changes are also essential. You can easily suggest throwing a method or class away, but you will rightly so have a harder time suggesting throwing away a module or system.

Refactoring is often used as a suggestion to combat the need to rewrite or throw code away but this is rarely the case in practice. Refactoring is a misused word and crucially misunderstood technique. If you change architecture you are not refactoring.

The biggest objector you will likely find is yourself. Having become invested in a task it can be hard to try again. Fight the urge to resist and throw code away. You may be pleasantly surprised by the results.