> and they're allergic to automation, hiring higher quality engineers, and hiring more engineers to improve velocities I think there's another issue, but it co

> and they're allergic to automation, hiring higher quality engineers, and hiring more engineers to improve velocities I think there's another issue, but it could relate to your first two statement here. Even to try ideas, to explore the space of solutions, you need to have ideas to try. When entering development, you need clarity on what you're trying. It's very hard to make decisions on even a single attempt. I see engineers working task the entire time simply not sure what really the task is about. And in a way, the coding agents need even more clarity in what you ask of them to deliver good result. So even inside of what we consider "development" or "coding", the bottleneck is often: "what am I supposed to do here?" and not so much "I don't know how to do this" or "I have so much to implement". This is obvious as well, once you throw more engineers, and you can't break up the work, because you have no clue what so many people could even all do. Knowing what all the needed tasks even are is hard and a big bottleneck.