The better your code is architected, the less powerful model you’ll need for it to make sense of it.

E.g. a well-designed deployment (infrastructure-as-code) repository doesn’t need a frontier model to be understood well-enough to create a new job / service using sibling jobs / services as templates.

And this already saves me dozens of minutes per week, although it’s not a 2x multiplier in my efficiency.