That brings up a question. What do you call it when a capable person keeps a tight leash on the process, making deliberate design decisions as you go, based on a well considered plan?
Vibecoding seems very wrong. That implies someone yolo’d a prompt at something with “dangerously accept” enabled.
It’s not conventional development, as the llm is writing most-or-all of the code.
Is it maybe where this post settled on “agentic engineering”? It does describe full requirements gathering, writing everything up like you’re supposed to, documenting, etc.
What is a tight leash? Human developer and human reviewer? Or is AI reviewer good enough? ...
Couple years ago people were copying code from other parts of a codebase or stackoverflow, now they copy it from some blackbox AI.
Do we need a special way of calling it? How did we call people using stackoverflow?
I mean I can't speak too much on what best practices always ends up looking like (the gap between law and reality is always there) but I think the issue with agentic engineering is crucially the fact it compresses the time and effort in all these tasks; you can plan, write the code, and do all the parts in one session and then if there's a bug it's much harder to track done, especially if that would have surfaced early on in reviewing the plan. So really the slowness and review is what's gone and that's albeit what's needed more than ever.
So it's not vibe coding anymore. Now it is agentic engineering. I just can't...
That brings up a question. What do you call it when a capable person keeps a tight leash on the process, making deliberate design decisions as you go, based on a well considered plan?
Vibecoding seems very wrong. That implies someone yolo’d a prompt at something with “dangerously accept” enabled.
It’s not conventional development, as the llm is writing most-or-all of the code.
Is it maybe where this post settled on “agentic engineering”? It does describe full requirements gathering, writing everything up like you’re supposed to, documenting, etc.
What is a tight leash? Human developer and human reviewer? Or is AI reviewer good enough? ... Couple years ago people were copying code from other parts of a codebase or stackoverflow, now they copy it from some blackbox AI.
Do we need a special way of calling it? How did we call people using stackoverflow?
Tastemaxxing. It's the new moat, bruv!
Codesmithing
I mean I can't speak too much on what best practices always ends up looking like (the gap between law and reality is always there) but I think the issue with agentic engineering is crucially the fact it compresses the time and effort in all these tasks; you can plan, write the code, and do all the parts in one session and then if there's a bug it's much harder to track done, especially if that would have surfaced early on in reviewing the plan. So really the slowness and review is what's gone and that's albeit what's needed more than ever.