Earlier quoted context omitted.
I think it's a U-shaped utility curve where abstract planning is on one side (your comment) and the chore implementation is on the other. Your role is between the two: deciding on the architecture, writing the top-level types, deciding on the concrete system design. And then AI tools help you zoom in and glue things together in an easily verifiable way. I suspect that people who still haven't figured out how to make…
You don’t empathize with the humane opinion “why bother?” I like to program so it resonates. I’m fortunate to enjoy my work so why would I want to stop doing what I enjoy?
Just like you should be able to say something positive about Javascript (async-everything instead of a bolted-on async subecosystem, event loop has its upsides, single-threaded has its upsides, has a first class promise, etc) even if you don't like using it.