[andrewstuart2]

I'm on board with your gut that this feels more YOLO than careful but to be fair, in the engineering world fly by wire is very much precedented. I'm specifically thinking of the B2 bomber where it's essentially unflyable without a computer between the inputs and the outputs. Partially just keeping the plane from turning into a frisbee by reacting faster than a human possibly could, but also treating the controls inputs as the intent and manipulating the control surfaces programmatically in order to make that work. It's not quite the same thing of course but I think there's some carryover.

Still. Not a huge fan of this announcement or the general ways the landscape is evolving these days.

[conciliatory]

This is a great analogy to what this time in IT and tech feels like. We are moving up a layer in terms of abstraction, and for those of us who cut our teeth in processes where we had lower level understanding it feels very destabilizing. I've been telling my team for a few years now that becoming an "agent manager" is the path forward - it's more true now with the latest revelation that "managers are out of style", and every role will have some IC component. I've seen it in my work - I can express intent more clearly to Claude and get immediate feedback for any technical tasks, so my team needs to be able to create intent at a higher level and translate that to their agent team, rather than getting directive task alignment. We've been through these pendulum swings before - this should start to stabilize in a few years... That's the industry vet perspective - I'd be lying if I said it didn't feel different this time though...

[jurgenburgen]

> We are moving up a layer in terms of abstraction

I’ll believe it when I don’t need to understand the code. Until then it’s just autocompletion with (a lot of) extra steps.

Wake me up when I can actually let agents do the IC work without having to be the accountability sink that gets fired when things go wrong.