If you’re not doing that and just blindly committing whatever code the LLM generates without so much as glancing at it, you’re not adding any value and there’s a good chance that with a little initial guidance, the janitor could perform your prompt-jockeying about as well.

Creating the correct prompts to address specific concerns and goals requires technical knowledge and problem solving skills, same as before LLMs. Now, there's less typing of the code. Ofc 40 file changes indicates management is failing, leaving little confidence they could prompt their way to intended features. Code storms should be a converted to a stacked pr on a feature branch, so it is reviewable with great confidence. These words describing these issues require a level of sophistication which will necessarily no longer be a people manager role. I think this kind of (nearly) codeless position is ahead of the curve, not behind.

Whether someone else will be left cleaning up the mess (I have been in that position) is a separate question.

I couldnt not put this here. I have people skills.