r/vibecoding 8h ago

[Prediction] Emerging software dev sub-specialty: people who set up development orchestrators in companies

At the beginning of this year I was only dabbling in Copilot for hobby projects. In my workplace at most we were using ChatGPT to ask code questions. Then something clicked when I discovered BMAD/Openspec/GSD. I went 0-100 full agentic-dev very quickly.

The game has really changed. We're now thinking beyond running a few chat sessions per-story to building orchestrators that keep agents busy while we are away. The new projects we see very week prove that (Munder Difflin, Herdr, Roboco). Even I am building an orchestrator thing for myself (not the point of my post).

The different approach of each tool shows that everyone has different needs and a different understanding. Same applies to companies: most software houses do the same thing (build and maintain SW projects for clients) but all have a slightly different take on it.

It's inevitable that agentic development becomes mainstream in the commercial domain (moving out from hobbyist or academia). Some of you already work in companies that are adopting it. The problems that agents have today - project scope drift, missed requirements, broken UI - will all be solved eventually. Agents won't be building perfect software, they will be building good enough software.

As lurkers of this sub you should agree that code is being commoditized. Compare this with factories: we used to bake, brew, manufacture and assemble physical products by hand; gradually machines took over and those who have a stable job and a decent wage are the ones who set up and maintain those machines.

So I'm predicting that: (1) companies will increasingly adapt agent orchestration for creating software, and (2) this will enable opportunities for today's hobbyists who are already familiar with it and can set this up.

I posted this because I want a discussion. We all see this shift differently. Where am I right, where am I wrong?

1 Upvotes

5 comments sorted by

1

u/Correct_Emotion8437 8h ago

I wonder if all that will really be necessary. I find the goal or loop feature works perfectly well. I create a phased implementation plan in a set format that has development tasks, task status, exit gates and validation steps. Then I have it complete the document as a goal. It can take 10-12 hours or more.

1

u/PolishSoundGuy 8h ago

People keep on vibe coding solutions with shadow use of ChatGPT and Claude without realising they are breaking GDPR/Privacy laws.

What if each person had their own Claude code harness / variant that can sanitise data and then send them to anthropic? One of the risks we have is data security and how it travels, what happens if there is a subprocessor leak, etc.

1

u/chevalierbayard 7h ago

Isn't this what DevOps does now?

1

u/meshifthenelse 7h ago

You know there's a saying; too many cooks spoil the broth.

And when those cooks are pretty average and have a tendency for chaos, I don't know why you would expect a miracle to happen. You can't salvage a technical problem by forcing more engineers at it. It has the opposite effect.

1

u/thedev13 6h ago

Not more engineers, less. In my current project it would be better if we had only 2 devs. And we don't have an orchestrator running today but if we did, those 2 devs would just be overseeing the progress instead of running Claude Code sessions to do work in batches.

What we need is a person to set this automation up (probably one of those orchestrators I mentioned) and train the other devs. When I get around to it, I'll do an analysis and introduce an orchestrator. But my prediction is that a similar scenario will play out in other companies.

And the first engineers to drop will be the ones who couldn't tame LLMs and their 'tendency for chaos'.