[majormajor]

> We should be aiming more towards making projects with a scope that we can actually manage, instead of trying to build huge castles of sand and failing spectacularly. And of course continue to improve our tools to properly manage more complexity.

Its rarely the developer who decides the size, scope, and complexity of the project.

Reliability/extensibility/dev speed/complexity all trade off against each other, but if you're working for someone else, you have to present those tradeoffs to the right stakeholders, not just always choose simpler.

There's also the "knowing the future" problem - the right design for today might run into a wall when the assumptions or business goals change tomorrow.