Many of you have this job: Orchestrator

I still think naming things is more important than ever.

You can let the LLM decide how to name things, and spend days or weeks refactoring things. Or you can get your sketchpad out and invent/derive Correct names for methods, api methods, database schema, and so forth, and save yourself a lot of trouble.

The LLM is great at elaboration, but bad at inception, that is, bad at starting off from a blank canvas accurately for a long-lived project. That's where human creativity and genius come in. Not in the elaboration, but in the seedling.

In the orchestration metaphor, it's as if you give the LLM a blurry blob of reality and it starts playing music on it. You clarify, that's a saxaphone, or that's a cello, and suddenly it holds it correctly and plays it with sophistication. If you neglect fair naming or good-naming of your methods and needs, the LLM does its best guess on what this blurry blob of reality is, and it is often a blurry result to accompany.

It's kind of like assembly moving to C moving to Python, etc...

That does not mean the need to C and assembly developers will disappear.

Same thing with "manual coding" and "orchestration"(or what ever you want to call it). Just different levels of the stack.

It's different levels of the development stack and system's orchestration lives on top of the application level.

Key point here is that it isn't a new kind of "developer," it's an entirely different approach.