That assumes that you know upfront what you will need and what software design will best meet the need. Sometimes that is the case, but many times it isn't. Different strategies are needed to deal with the latter case.
I say design and not just plan because you'll want to mock out or prototype something to show and that does take design work to keep your iteration cadence high.
In my mind flexible means easy to iterate on but maybe that is not clear.
Accidental complexity is something you should work hard to avoid. Trying to avoid essential complexity however is a fools errand and if you try, it will result in a deck of cards that only work under perfect conditions.
This is impossible for anything more complex than the simplest of toy examples. Never have I seen a production system where all behaviors and use cases are known, well-defined and correctly documented ahead of (or even after the) implementation in enough detail. That’s just not how people operate.
It’s the equivalent of saying everybody should just come together and talk it out to achieve world peace.
We call that waterfall :)
And it can be really hard to tell the difference
I’m wondering if ML will get good enough to produce PR reviews that comment on style and refactoring opportunities to match the codebase’s spirit.