SDD vs Vibe Coding¶
February 20, 2026 · LinkedIn
23 reactions · 8 comments · 1,552 views
A few weeks ago I asked a room of developers two questions.
First: "How do you use AI in your work?"
Great answers. Specific. Confident.
Second: "What does your team's AI workflow look like — the shared one?"
Silence.
That gap — between individual fluency and organizational capability — is the one I don't think has a name yet.
Vibe coding. Agentic engineering. Both real. Both individual.
What the best teams are building is something else: deliberate, shared, transferable. Human skill leading. AI executing. Capability that compounds. Real productivity increase across the board.
We've started calling it Skill-Driven Development.
Most teams are somewhere in the middle right now — and most don't know which direction they're drifting.
Discussion¶
It's fascinating how individual skills can be amplified through teamwork. : It's fascinating how individual skills can be amplified through teamwork.
Totto ↩: Matthias Herbert Absolutely — when it's intentional. The gap I keep seeing is that most teams assume it happens naturally. It doesn't. What does that look like in practice for your team?
yeap, I call it development guardrails in our company ;) as now the guardrails are also part of the code... because when there is a we sort of emerges a way of doing that is beyond the individual is about the "team" or sometimes the cto decision ... depending on how flat is the organization: yeap, I call it development guardrails in our company ;) as now the guardrails are also part of the code... because when there is a we sort of emerges a way of doing that is beyond the individual is about the "team" or sometimes the cto decision ... depending on how flat is the organization