Developers have always been the first to feel the full force of AI. They were the earliest adopters of copilots, the first to hand off entire codebases to agents, and the first profession to get a catchy name for the new way of working. But coding was just the beginning. The patterns that emerged in software development are now spreading to law, medicine, and virtually every knowledge profession. The question isn't whether "vibe coding" applies beyond code. It's what happens when it does.

Where vibe coding started

In February 2025, Andrej Karpathy posted a now-famous tweet describing a new way he'd been writing software. He called it "vibe coding," a workflow where you "fully give in to the vibes, embrace exponentials, and forget that the code even exists." He described accepting all AI-generated changes without reading diffs, pasting error messages back into the chat with no commentary, and letting the codebase grow beyond his own comprehension. The term struck a nerve. Within weeks it had a Wikipedia entry. By the end of the year, Collins English Dictionary named it Word of the Year. It resonated because millions of developers were already doing the same thing, they just didn't have a word for it yet. The core idea was simple: instead of writing code line by line, you describe what you want in plain language, let the AI generate it, and steer by outcomes rather than implementation. You become a director, not a typist.

Developers as the canary

There's a reason this happened to developers first. Software is uniquely suited to AI automation. Code is structured, testable, and deterministic. You can verify whether a program works by running it. Feedback loops are tight. And the entire history of programming is, in some sense, already in the training data. This made coding the perfect proving ground for large language models. GitHub Copilot arrived in 2021. By 2024, coding agents could handle multi-file changes. By early 2026, Karpathy himself moved on from "vibe coding" to a new term, "agentic engineering," describing a more mature workflow where developers direct AI agents with high-level oversight, judgment, and taste while the agents handle implementation. The pattern is clear: AI capabilities land in software first, then radiate outward. Coding agents came first. General-purpose agents are coming next.

What if we apply this to everything?

Here's the thought experiment. If AI can write production-ready code from a plain-language description, why can't it do the same for a legal contract? A medical diagnosis? A financial analysis? In many cases, it already can, at least partially. Law. AI tools are already transforming legal work. According to Thomson Reuters' 2025 Future of Professionals Report, AI-driven productivity tools for document review, legal research, and contract analysis could save lawyers nearly 240 hours per year. Harvey, a legal AI platform, is building sector-specific agents for the legal industry. The term "vibe lawyering" has already started circulating, describing lawyers who prompt AI to draft agreements and briefs, then review the output rather than writing from scratch. Medicine. Google's Med-PaLM cleared the US Medical Licensing Exam with expert-level scores. AI systems can now read radiology scans, suggest differential diagnoses, and summarize patient histories. The idea of a doctor describing symptoms in plain language and getting a diagnostic workup isn't science fiction anymore. Finance, consulting, operations. The same pattern holds. Describe the output you want, let the agent generate it, steer by results. Gartner predicts that 40% of enterprise applications will embed task-specific AI agents by 2026. In each case, the professional's role shifts from doing the work to directing and verifying the work, exactly the way developers shifted from writing code to guiding agents.

Vibe lawyering, vibe doctoring, vibe everything

If vibe coding means "describe what you want, accept the output, and iterate by vibes," then what does that look like in other fields? Vibe lawyering might mean prompting an AI to draft a non-disclosure agreement, scanning the output for obvious issues, and sending it to the client. You don't write the clauses yourself. You don't care about the specific legal phrasing, as long as the intent is captured and the risks are covered. Vibe doctoring might mean describing a patient's symptoms to an AI, getting a ranked list of likely diagnoses with supporting evidence, ordering the recommended tests, and trusting the system unless something feels off. Vibe accounting might mean feeding financial data into an agent, asking it to prepare quarterly reports, and reviewing the summary rather than building every spreadsheet by hand. The pattern is always the same: shift from execution to oversight, from craft to direction.

The uncomfortable part

This is where things get interesting, and uncomfortable. When Karpathy described vibe coding, he was careful to note it was "not too bad for throwaway weekend projects." The code he was producing wasn't mission-critical. He wasn't building aircraft control systems this way. But what about a legal contract that determines custody of a child? A medical diagnosis that decides whether someone gets surgery? A financial report that moves markets? The stakes are fundamentally different. In coding, you can run tests. You can deploy to staging. You can roll back. The feedback loop is fast and the cost of failure is often low. In law and medicine, the feedback loops are slow, the stakes are high, and errors can be irreversible. You can't "roll back" a wrong diagnosis or a flawed contract that's already been signed. This is the core tension: the workflow of vibe coding, describing intent and letting AI handle execution, is transferable to almost any knowledge profession. But the attitude of vibe coding, accepting output without careful review, becomes dangerous when the consequences are serious.

From vibes to agentic engineering, everywhere

This is exactly why Karpathy's evolution from "vibe coding" to "agentic engineering" matters beyond software. Agentic engineering keeps the productivity gains of AI-assisted work but adds back the human judgment layer. The professional still directs the AI. The professional still reviews, verifies, and takes responsibility. The AI handles the execution, but the human provides the oversight, the taste, and the accountability. For lawyers, that means using AI to draft contracts but carefully reviewing every clause. For doctors, it means using AI to suggest diagnoses but applying clinical judgment before acting. For any professional, it means embracing the leverage that AI provides while maintaining the rigor that the work demands. The future probably isn't "vibe doctoring" in the reckless sense. It's agentic medicine, agentic law, agentic finance, a world where professionals direct AI agents with expertise and oversight, achieving in hours what used to take days.

What this means for everyone

Developers experienced the future of work before everyone else. They went from writing every line of code to directing agents that write code for them. They coined a term for it, debated its limits, and evolved the practice into something more disciplined. Every knowledge worker is about to go through the same transition. The tools, the terminology, and the cultural adjustment are all coming. The question for each profession isn't whether AI will change the workflow, but how much oversight is appropriate given the stakes. The vibe coders figured this out first. Everyone else is next.

References