< How... How do I think properly? How do YOU think? Share your thinking thoughts!
I may not be the best reference, but I've found a good approach with programming: always have one to three problematic areas until the program is finished.
Trying to improve your code before writing it makes you inefficient, and often you have to remove that work anyway when something about the design inevitably changes. However, if you're constantly growing in code debt then you'll need to go back anyway, so that's also inefficient.
When your areas of gross-ness are in the single digits, you're iterating quickly but keeping the mess at a managable scale. I hope that makes sense haha
Source