I always get stuck when I need to pick the right architecture for new features or projects. I end up thinking too much about different ways to structure things and make everything way more complicated than it needs to be. This slows me down a lot and creates messy code that’s hard to work with later. I want to get better at making quick decisions about code design and write simpler solutions that actually work well. What books or learning materials helped you improve at this? Any specific methods or approaches you recommend for avoiding this trap?
oh i totally feel this! what kind of projects are you usually working on when this happens? is it more backend stuff or frontend components? i’ve noticed my overthinking gets worse with certain types of features and was wondering if theres a pattern for you too?
for sure! i used to struggle too but now i focus on getting a working prototype up quickly. like, don’t let perfect be the enemy of good, y’know? simplicity is key, and you can always iterate later if needed.
To address the challenges you mentioned, I recommend starting with a clear hierarchy of priorities before you code. Focus on the simplest implementation that meets your core requirements, then outline a few specific areas where future improvements could be made.
Adopting a ‘prove it first’ mentality can be significant. Instead of planning for every possible scenario, aim for a minimal viable solution and wait for actual issues to surface. This often prevents unnecessary over-engineering.
Set strict time limits for making architectural decisions; dedicating just 30 minutes to evaluate options and documenting your choice can help eliminate decision paralysis. Lastly, I found ‘A Philosophy of Software Design’ by John Ousterhout particularly valuable in managing complexity.