Programming

Right? That is not my preferred skill set and I don't enjoy those things. I like understanding and designing patterns. I like feeling connected to the code and problems I'm solving, and I like feeling clever when I come up with solutions.

AI takes all of that away. It's got more data than I can ever cram in my skull, more energy than I'll ever have available to me, and it's being forced on us at every corner so it has access to things I'll never see.

Honestly I would be okay with LLMs if they weren't killing our planet and robbing us of our humanity and creativity.

That's a terrible take and its desperately trying to draw an equivalence where there isn't one.

I'd argue that the slop code creates more drudgery with having to constantly babysit the LLM. Never mind a new blog post every week about how your "agentic workflow" from last week is all wrong and you need even more infrastructure to wrangle the LLM. It's worse than the way the JavaScript ecosystem used to be!

Reading someone else's code is challenging, but at least with a person you can ask them questions or debate.

I guess I'm just someone who finds reviewing someone else's work tedious, though a necessary part of the job.

To each their own I suppose. By which I mean maybe the author enjoys different parts of coding than you do. Trying to wrangle AI into writing something decent is generally an exercise in frustration for me. But I enjoy architecting and figuring out how to define units of work that are small and self-contained enough to get AI to understand.

I've been mulling over what kinds of architectural changes might make it easier for AI to be able to contribute. That’s a puzzle I find interesting in the same way I enjoy other programming problems.