It handles DevOps tasks way faster than I would - setting up infra, writing migrations, config changes, etc. Project is still early stage so speed and quick iterations matter more than perfect process right now. Once there's real traffic and a team I'll tighten things up.

"Once there's real traffic and a team I'll tighten things up."

As someone who has been in this industry for a quarter century: no, you won't.

At least, not before something even worse happens that finally forces you to.

If I felt the need to optimise things like infra setup and config at an early stage of a project, I'd be worried that I'm investing effort into the wrong thing.

Having an LLM churn out infra setup for you seems decidedly worse than the `git push heroku:master` of old, where it was all handled for you. And, frankly, cheaper than however much money the LLM subscription costs in addition to the cloud.

But why have it execute the tasks directly? I use it to setup tasks in a just file, which I review and then execute myself.

Also, consider a prod vs dev shell function that loads your prod vs dev ENV variables and in prod sets your terminal colors to something like white on red.

> Once there's real traffic and a team I'll tighten things up.

Nope. Once there's real traffic, you'll be even more time-constrained trying to please the customers.

It's like a couple who thinks that their failing relationship will improve once they have a child.

If you have no real traffic, what complex things are you doing that even require such tools?

There is nothing more permanent in computerlandia than a temporary solution.