I believe the best solution right now may be to get an MVP without worrying about technical debt too much while not purposely doing things to step on your own feet while acknowledging you'll need to do a full rewrite before 1.0.
I used to think that way, then I realized that I should worry about building a product people will pay for before worrying too much about technical debt.
It's almost a Maserati problem when you think about it.
i think that is the right way to think on most software projects. But on projects that require rapid iteration and user testing(such as hit-based projects like games), technical debt could cause your iteration rate to be slowed to a crawl, and in the end you produce an inferior product.
Had the technical debt been paid up front, the iteration rate might have been much faster (e.g., good encapsulation and abstraction allows you to switch out things quickly to test different mechanics in a game), leading to a better end product that people will pay for.
