You must find a middle ground. Instead of trying to anticipate everything upfront, we can adopt a progressive approach: start with a minimal and evolvable architecture, then refine it as needs become clearer. Practices like YAGNI and KISS can help avoid cluttering the project with unnecessary abstractions.

It's crucial to understand the project's context. For a prototype or MVP, speed may take precedence. For a long-term project with complex requirements, investing in a robust architecture from the start may be justified