Sustainable engineering – avoid big re-writes

By October 5, 2015Forward Partners

Last week friend of Forward Partners Douglas Squirrel published a post about Sustainable engineering on The Path Forward in which he advises founders on how to scale their engineering effort. When the focus is on validating the idea and building first versions of the product it usually makes sense to take shortcuts in code and process quality to accelerate learning, but when the focus shifts to scaling the company it’s important to shift to scalable and sustainable software development practices.

Squirrel’s advice is to eschew ‘big bang’ changes such as re-writing in a new language or framework in favour of incremental changes using techniques like ‘inline’ refactorings and ‘spike stories’. ‘Big bang’ changes nearly always come in late, over budget, and under specification whilst incremental techniques have lower risk and keep the feature set moving forward. Interestingly given he’s an experienced startup CTO himself, Squirrel says to be wary of the advice of developers who “always want to re-write everything”.

If you are in this situation, or think that you might be I highly recommend you read the full post.

Our plan is that more and more authors like Squirrel will become Pathfinders and contribute to The Path Forward. Squirrel is actually our second Pathfinder, the first was Matt Buckland, who used to work here but is now Head of Talent at Lyst. He wrote a about How to read a CV and we have more articles from him coming in the near future.

If you would like to become a Pathfinder let me know via the comments or otherwise reach out.