[itmitica]

I too was convinced at one point the spec is the program.

That it doesn't matter the implementation stack.

But, after wasting too much time in the meta, with nothing really to show for, I returned to controlling the programming process in fine detail. Progressive agentic/vibe coding, if I was to give it a name.

But it could be that I'm slow to understand how it can be done in a better way.

[edg5000]

I think this progressive/gentic vide coding would work better if the tools were better and storing the history in a good immutable way, kind of like an email program. I have very valuable sessions where I give the agent a good ephemeral spec, something not sensible to persist in the codebase, but important enough to track it somewhere. Throwing away history is a big no no. Bad GUIs/TUIs discourage from relying on the history. When I close a session, I feel I'm throwing away the history. I keep many terminals open, but eventually have to close them. Tools will get way, way better to facilitate this "general on the frontlines commanding the agents" style of work.

[tarasyarema]

I believe that it’s a matter of evolution. You start small and find what works fir you and the project. Then iterate and see how to remove yourself from it more.

I actually wrote about this concept here if that’s something the might interest you: https://www.tarasyarema.com/blog/2026-02-18-introducing-sema...

[itmitica]

I like your content very much, let me point this out first.

I'm not sure all aspects are covered in the approach.

For instance, controlling the agents takes a big chunk of the interest. The agentic system architecture is also big in view.

But, the way I see, more important staff is: project structure, coding best practices, testing strategies. All still deterministic. All still very tough to get agentic to do it right.

I think agentic should just be means to an end: project quality and project ease of management. If not, it's just an indulgence that costs money.