The 77% Who Never Coded Don't Need To
Describe what you need. AI handles execution. That's vibe working.
Vibe coding was the developer's revolution. Programmers describing what they wanted instead of writing every line. It changed how software gets built.
Everyone focused on developers. Wrong audience.
The real shift is vibe working. It has nothing to do with code.
Everyone Missed This
In December 2025, Cambridge Dictionary added "vibe coding" - completing tasks by giving AI a general idea instead of detailed instructions. Developers celebrated. They could build software by describing intent.
The tech press covered it as a programming story. They were wrong.
What Cambridge captured wasn't a coding phenomenon. It was the beginning of a work transformation. By focusing on "coding," they missed the bigger picture.
Azeem Azhar saw it more clearly. In Exponential View, he described the shift as "using AI to turn rough ideas into finished work through back-and-forth." Not rough code into working code. Rough THOUGHTS into finished OUTPUTS.
Programming was never the point. Work was.
77%: Not Coders, Just Working
I've onboarded 53 professionals into Second Brain - a system that helps knowledge workers use AI. When they start, I send each customer a personalization questionnaire. Technical background. Work patterns. What they want to accomplish.
The data from those questionnaires:
77% had never touched Claude Code before. Never opened a terminal. Never wrote a script. Never will.
74% identify as non-technical. Consultants. Founders. Content creators. People whose expertise is their domain, not technology.
Most are 40-50 years old. They built careers on relationships, expertise, and accumulated wisdom. They ignored the tech boom. Built careers on relationships instead.
The key insight: they stayed non-technical. They just started doing their actual jobs differently.
The 77% stat tells a work story, not a technology story.
What It Actually Looks Like
When I track what users do first, the pattern is clear. Not technical. Operational.
Weekly planning leads with 6 mentions: "I have three client calls, a board meeting, two deliverables. What should I focus on?"
Content creation follows at 5 mentions: "Explain to clients why our approach changed. Honest but confident."
Meeting prep at 4 mentions: "I'm meeting Sarah Chen tomorrow. She's been skeptical of our progress. Pull what I need to address her concerns."
Proposals round it out at 4 mentions: "Pitching a 6-month engagement to a CPG company. They care about speed. Their previous vendor was slow."
No code. No building. No systems. Just work described in plain language, with AI filling in the execution.
Dominic Albrecht, 45: "I'm not a coder. I don't write code. I just... describe what I need done."
He's not building anything. He's working.
Why 'Vibe Coding' Is a Trap
Vibe coding got all the attention because it was measurable. Developers could point to shipped software. They could show before-and-after code. The productivity gains were tangible.
But that framing trapped the conversation in a technical box. Every article about "AI for non-coders" still talked about code. Building. Systems. Tools.
Wrong metaphor entirely.
A consultant using AI to prepare for a client negotiation isn't building a negotiation system. She's doing her job. The preparation. The thinking. The anticipation of objections.
Or the founder drafting investor updates - he's not automating anything. He's writing, revising, finding the right tone.
Vibe working means AI-assisted work for everyone, not just tool building for the non-technical.
Microsoft's September 2025 framework called it "human-agent collaboration where AI generates, tests, and refines multi-step work while you steer."
Steer. Not build. Not code.
The Real Shift
If vibe coding required developers to articulate intent, vibe working requires something simpler: knowing your work.
Know what a good proposal looks like in your industry? You can vibe-work a proposal. Know what preparation means for your types of meetings? You can vibe-work meeting prep.
You don't need technical skills. You need to know your domain and describe it clearly.
Richard Wilson's reaction after his first session: "Holy shit. I didn't know this was possible for my actual job."
He wasn't excited about building systems. He was excited because his work - the consulting, the client prep, the strategic thinking - could happen faster and better.
Damian Nomura built a client proposal system in two days. Companies charge $50/month for worse versions. He wasn't proud of building a product. He was proud of what he could now DO.
Why Now
The vibe coding discourse peaked. Developers integrated it into workflows. The novelty faded.
Vibe working is just beginning.
Every knowledge worker - every consultant, founder, analyst, writer, strategist - does work that can be described. High-level intent that expands into detailed execution.
57% of our users started with personal workflows. They didn't ask for systems. They asked for help with THEIR work. Their week. Their meetings. Their proposals.
32% then extended what worked to their teams. Not by deploying tools. By showing colleagues a new way to work.
The technology is ready. The bottleneck isn't capability.
It's how people think about AI. They still believe they need to build something or code something or become technical.
They don't.
The 77% describe their work and watch it get done differently. No systems. No code. Just work.
If you're a consultant, founder, or knowledge worker, you don't need technical skills. You need to know your domain. You need to describe what good work looks like.
You've spent decades learning that.
The rest is iteration.
Second Brain helps knowledge workers transform how they do their actual work. No coding required. Learn more at iwoszapar.com/second-brain-ai.
Related reading: whether AI will democratize or kill consulting · whether AI actually makes consultants obsolete · how HR teams are revolutionizing work with AI · what setting up everyone else's second brain taught me