Assisted coding
- Interaction
- Suggestions inside the editor
- Human role
- Writes, reviews, decides
- AI role
- Proposes local code
- Evidence
- Human inspection and checks
- Best fit
- Local, understood changes
Observations
from building.
Ideas documented.
From Vibe Coding to Agentic Engineering
AI coding started as assistance inside the editor. It is becoming a system for delegated work, and that changes what engineers need to design.
Read the noteOperating model / 01
Three modes of AI coding
The model improves, but the deeper change is who controls the work.
Vibe coding
- Interaction
- Prompt, run, correct
- Human role
- Steers by visible result
- AI role
- Generates the implementation
- Evidence
- What appears to work
- Best fit
- Disposable experiments
Agentic engineering
- Interaction
- Delegate a bounded task
- Human role
- Designs and accepts the system
- AI role
- Executes and revises in a loop
- Evidence
- Independent checks and review
- Best fit
- Repeated or consequential work
Recent notes.
01
How coding moved from editor assistance to delegated work inside explicit task, authority, evidence, and acceptance boundaries.
↗02
A practical model for deciding when an AI-assisted change is complete enough for an engineer to accept responsibility for it.
↗03
A test for separating model-specific behaviour from the task, permissions, evidence, state, and acceptance controls that should remain.
↗I rarely write because I know.
I usually write because I think I’m getting closer.
New notes, when there’s something worth keeping.
No fixed schedule.
Follow by RSS