[hasbroslasher]

This is some great advice in my opinion. Every project starts from a base - give it a shitty base, and you're always going to have problems. Spend the time to write an OK base that doesn't try to do anything clever but organizes code in a clear and sane way and you'll be reaping the dividends for years to come. There is nothing more valuable than, from day one, unit testing, organizing files in a clear way, preventing clutter, and starting writing basic documentation of how to work with your software. These simple cues will remind you and others of what the expectations are for your project.

As popular as it is to say "just solve the problem in front of you", no one actually does that. No one sits down to work on something with one problem - the sit down with likely hundreds, all vying to be solved. Average engineers will look at one, solve it, test it, put it in a text file, push it to prod, and say "look, done!" Good engineers will look at the whole class of problems and recognize commonalities that inform basic architectural and infrastructural decisions.