And regarding the gym, sure, you might enjoy lifting dumbbells and solving puzzles to sharpen your brain. But that is not what engineers are hired for; they are hired to deliver a system using the best tools available. You can choose to farm by hand while the industry moves to using tractors, but sooner or later, you will be left behind.

And lastly, moving higher in abstraction allows us to tackle even more complex problems—I'd argue much more complex than the narrow puzzles we were facing before. Part of the resistance is simply an avoidance of facing higher-level complexity once the lower tier is automated.

* https://repo.autonoma.ca/repo/treetrek/tree/HEAD/render/rule... - syntax highlighting for 40 languages and file formats in ~10 minutes

* https://shufflenblues.com/expenses/ - real-time expenses progress updates with payment vendor API in ~30 minutes

* https://repo.autonoma.ca/repo/treetrek/tree/HEAD/git - real-time, cache-free raw Git reader implementation with cloning in ~5 days

* https://repo.autonoma.ca/repo/notanexus - PDFjs integration in ~3 days

However, these are likely not the "hard" problems you've mentioned. I feel like I can architect solutions at a higher-level now, without having to be completely caught up in many technical nuances. I'd rather not learn the extensive PDFjs API, for example, because it would take weeks of effort to understand.

I just don't know how many people have an overly negative opinion on AI assisted coding because they've just used the poor versions of these products given out for cheap/free. A similar critique is basing one's opinion on AI based on summary that Google provides for free in their search.

But isn't the strawman here was that it wasn't a spectrum. That they couldn't just use it some, but all or nothing.

That's because AI wrote it to deter other AI from taking it's job

"woodwork is just procrastination that gets in the way of implementing your ideas."

We can find plenty of others, but my main point is that industrializing a process doesn't make it "procrastinating". There are plenty of jobs that are done by machines but are still practiced by humans for multiple reasons. If we think of coding as a means to create, then we have plenty of examples of good reasons to have both the industrialized process and the 'handmade' one.

- They dangerous both to me as a driver, my passengers, and other road users, including pedestrians and bicyclists.

- They ruin cities which constantly have to accommodate ever increasing number of cars by destroying previously walkable neighborhoods to make room for roads and parking.

- They destroy our climate

- They are loud.

- Busses are nicer and I can read a book while riding the bus.