When to Rewrite from Scratch - Autopsy of a Failed Software · CodeAhoy
We had written the original system with a gun to our heads. We had to race to the finish line. We weren't having long design discussions or review meetings - we didn't have time for such things. We would finish up a feature get it tested quickly and move on to the next. We had a shared office and I remember software developers at other companies getting into lengthy design and architecture debates and arguing for weeks over design patterns.
Despite agile-on-steroids design, the original system wasn't badly written and generally was well structured. There was some spaghetti code that carried over from company's previous proof of concept attempts that we left untouched because it was working and we had no time. But instead of thinking about incremental improvements, we convinced ourselves that we need to rewrite from scratch because:
Read full article from When to Rewrite from Scratch - Autopsy of a Failed Software · CodeAhoy
No comments:
Post a Comment