Minimum Viable Product

Discipline in Prototyping

Writing software doesn’t require discipline, but writing good software does. I would argue that the vast majority of tech debt in projects results from PoCs/prototypes/spikes. The code from these typically aren’t intended to make it into production, but they almost invariably do in some capacity. “I won’t bother writing unit tests for this code, it’s purely exploratory.” The code grows… “It’s just a rough proof-of-concept.” …and grows… “It won’t make it to production!”