I agree on both points. You definitely need well structured code to make long term maintenance and development feasible. But, what is "well-structured" when y

I agree on both points. You definitely need well structured code to make long term maintenance and development feasible. But, what is "well-structured" when your app is only in your imagination and subject to many pivots? The way I proceed now: 1) write crap fast to get it out there and to also discover the potential pitfalls of a given structure 2) refactor as necessary (it takes off, pivots, performance blows, or it's a maintenance nightmare). Be fearless about junking entire parts of your old badly designed code if you think you are going to maintain this for a while. 3) see 2) 4) see 2) 5) Now that I have a stable structure I keep refining the code base knowing that even if it doesn't seem perfect, the way I've structured your code is the result of several iterations, and is therefore probably as good as it's going to get. [edit for formatting.]