> So not really work, then?
I work like the parent poster does. I am working harder than before the AI tools came around. I am just working at a higher level. Not too dissimilar from someone moving from programming in assembly language to significantly higher level language.
> as little of me in the loop as possible
You may be confused about this. If I am running just one loop at a time, you'd be right. What modern tools allow me to do is think more like a supervisor that has dozens of engineering teams available to him. I always have a long list of problems I need to solve. I used to sit with one and bang on it until it would pass acceptance criteria. Sometimes that took months. Now I just farm out each task to an agent orchestrator, provide it details on what I want done, a bit of design and architecture and acceptance criteria. I then step away from it and move to the next agent orchestrator and repeat the process for the next task. I usually have 6 or 7 large tasks being worked on at the same time. This is currently my personal limit. I can't babysit more than that. But as the models and harnesses get better I suspect I will have to do less babysitting and this process will get more autonomous.
It may sound like this process would remove the need for engineers. In my organization it is doing quite the opposite. As the organization figures out that we can do a lot more, we change our plans to build more. A lot more. Building still requires engineers, more than before, for us. But only those who can think like architects and can manage large teams of AI agents and orchestrators that work 24x7.