[thymine_dimer]

"What comes after vibe coding" is a different question to the one you're answering. Feels like your answer is about better vibe coding: I'm using a tiered document system. It's just docs all the way down. Seems to be working for me, ask in another ten years.

What comes after vibe coding? At some point the AI will be asking humans if its new software saves us time and whether we'd pay money for it. Until then, there'll be some level of humans-asking-AI to solve a problem, probably with coarser and less detailed spec at each step.

[andreirx]

Yes I think this is the current "standard" - keeping notes in tools like Obsidian and having agents query it, or peppering README.md files throughout the codebase. I call it "breadcrumbs" because I just leave things in the path for the agent to pick up on. But it doesn't answer questions like what are all the callers of this function? where is this data going? where is it coming from? So I'm trying to solve THIS part which is much more time consuming and prone to drifting in time.

Better vibe coding - maybe. I wanted to distance myself from vibe coding - trying to get agents to output more deterministic code as opposed to vibing. (if I understand vibe coding correctly it's stating your intention and letting yourself go wherever the agents are taking you)

I also think agentic coding is not going anywhere so I'm looking for ways to make it more appropriate for my job.