Where is vibe ops?

I’ve been doing a lot of AI augmented development with Cursor. Sometimes the editor. Sometimes the background agents.

The last week or two, the dev work has focused on building a new FastAPI backend service and trying out a corresponding Vue frontend web app.

I’ve already been adapting some of my tech decisions to be more suitable for AI development. Separate repos to keep workspaces simpler and require less instruction to agents. Leaning more on json API responses and a Vue SPA rather than my preferred htmx, because it lowers friction with AI code generation.

The remaining friction though has been very similar to traditional development. Setting up some CI required GitHub secrets, a shell script here or there, and some ssh config. Getting apache configured for the Vue + client side routes. Configuring some things at Supabase.

What I notice is there isn’t a low friction path to vibe my way out of the ops work. Maybe if I went all in on a fully managed service like replit, but I like running a Linux machine.

I would imagine the same things are happening inside the enterprise too. Dev teams might shrink or stabilize but the automation and ops work is probably stable if not increasing. And then there’s all the new vibe coders in the indie hackers world needing ops work and help.

Maybe we’ll see increased adoption of services like http://fly.io which have very strong cli and API interfaces? Maybe devops will become even more valuable?

As AI development rapidly regresses to a mean, ops doesn’t seem to have as clear a path ahead.

Perhaps there is opportunity here.