Once you’ve found traction, you’ll likely need to re-write your codebase... The problem with this approach is that once you've got traction, you will be in the

Once you’ve found traction, you’ll likely need to re-write your codebase... The problem with this approach is that once you've got traction, you will be in the worst possible position to re-write your codebase. I understand the allure of just getting features out when you're trying things and don't have many customers to worry about. But the old adage of 'always time to do it over but never time to do it right' applies just as well early as it does later. Resist the temptation to throw away all discipline because 'it's just a prototype and we'll re-write it later.' The reality is, if your product catches on, you're going to be living with that code for a long time. Move fast, yes, but don't move sloppy.