The only answer would seem to be an extra axis of rotation, but (a) doesnt work well with existing input methods, and (b) would be even more of a brain-breaker

But my biggest objection to this "engineering is over" take is one that I don't see much. Maybe this is just my Big Tech glasses, but I feel like for a large, mature product, if you break down the time and effort required to bring a change to production, the actual writing of code is like... ten, maybe twenty percent of it?

Sure, you can bring "agents" to bear on other parts of the process to some degree or another. But their value to the design and specification process, or to live experiment, analysis, and iteration, is just dramatically less than in the coding process (which is already overstated). And that's without even getting into communication and coordination across the company, which is typically the real limiting factor, and in which heavy LLM usage almost exclusively makes things worse.

Takes like this seem to just have a completely different understanding of what "software development" even means than I do, and I'm not sure how to reconcile it.

To be clear, I think these tools absolutely have a place, and I use them where appropriate and often get value out of them. They're part of the field for good, no question. But this take that it's a replacement for engineering, rather than an engineering power tool, consistently feels like it's coming from a perspective that has never worked on supporting a real product with real users.

It could be argued that it was all inevitable given the development of the Internet: development of social media, the movement online of commerce and other activities that used to heavily involve "incidental" socialization, etc. And maybe it was. But "we" are still the ones who built it. So are "we" really the right ones to solve it, through the same old silicon valley playbook?

The usual thought process of trying to push local "community groups," hobby-based organizations etc is not bad, but I think it misses an important piece of the puzzle, which is that we've started a kind of death spiral, a positive feedback loop suppressing IRL interaction. People started to move online because it was easier, and more immediate than "IRL." But as more people, and a greater fraction of our social interaction moves online, "IRL" in turn becomes even more featureless. There are fewer community groups, fewer friends at the bar or the movies, fewer people open to spontaneous interaction. This, then, drives even more of culture online.

What use is trying to get "back out into the real world," when everyone else has left it too, while you were gone?

Still are, for Cybertrucks

Right, and neither did the GP. They both offered the exact same two reasons, the GP just apparently doesn't find them as repugnant as the author

That's... exactly what the author said in the post. But with the argument that those are cynical and terrible reasons. I think it's pretty clear the "you" in "why would you want an AI" vending machine is supposed to be "an actual user of a vending machine."

Those proprietary blobs are either correct or not. If there are bugs, they fail in the same way for the same input every time. There's still no sense in which ongoing human verification of routine usage is a requirement for operating the thing.

There's no need for ongoing, consistent human verification at runtime. Any problems with the implementation can wait for a skilled human to do whatever research is necessary to develop the specific system understanding needed to fix it. This is really not a valid comparison.

Namespacing, sure. But is "We use gh:someguy/openai/llm-streaming-client to talk to the backend" (x50 similarly cumbersome names in any architecture discussion) really better than "We use Pegasus as our LLM streaming client"?