10 Leaders of Vibe Coding Every Software Developer Should Study

Developers need a different ranking than founders or investors

Developers face the deepest professional version of the change. AI can now produce large amounts of code, but the engineer still owns architecture, correctness and the decision to trust or reject generated work. That makes judgment—not prompt novelty—the core ranking criterion.

Developers should rank leaders by how clearly their work changes the craft of reading, reviewing, delegating, testing and owning code generated by machines. This list is therefore an editorial ranking for professional software developers and senior individual contributors. It uses the broader market meaning of vibe coding, not the claim that every person listed endorses unreviewed code or fits Karpathy’s narrow original definition.

The first pair define the tension between accelerated coding and professional accountability

#1 Michael Truell — The Cursor cofounder moving the IDE from autocomplete toward agent supervision

For working developers, #1 Michael Truell matters as the Cursor cofounder moving the IDE from autocomplete toward agent supervision. For developers, Michael Truell’s importance is rooted in his work as Cursor cofounder and CEO. He helped move Cursor from AI-assisted editing toward agentic software work and higher-level developer direction. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because his strongest claim to influence is the professional workflow layer, not the original coinage of the term.^[1]

#2 Simon Willison — The practitioner drawing a hard line around accountability and review

For working developers, #2 Simon Willison matters as the practitioner drawing a hard line around accountability and review. For developers, Simon Willison’s importance is rooted in his work as independent developer and AI tooling analyst. He documented the original definition and repeatedly separated carefree vibe coding from accountable AI-assisted engineering. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because his leadership is interpretive and critical, showing that a movement also needs people who define its limits.^[2]

Ranks three and four move the developer from author toward director of software-producing systems

#3 Andrej Karpathy — The researcher whose original definition forces developers to confront what they stop reading

For working developers, #3 Andrej Karpathy matters as the researcher whose original definition forces developers to confront what they stop reading. For developers, Andrej Karpathy’s importance is rooted in his work as AI researcher and educator. His February 2025 post named vibe coding and described delegating implementation to models while barely reading the generated code. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because the original concept was a playful, narrow practice rather than a blanket synonym for all AI-assisted development.^[3]

#4 Scott Wu — The agent-builder shifting engineering from keystrokes to delegated tickets

For working developers, #4 Scott Wu matters as the agent-builder shifting engineering from keystrokes to delegated tickets. For developers, Scott Wu’s importance is rooted in his work as Cognition cofounder and CEO. He made autonomous coding agents a mainstream engineering-management issue through Devin’s task-level and project-level delegation model. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because agentic engineering is adjacent to, but not identical with, Karpathy’s original low-review vibe-coding practice.^[4]

Positions five and six expose the new boundary between code creation and platform operation

#5 Guillermo Rauch — The web platform leader making deployment context part of AI development

For working developers, #5 Guillermo Rauch matters as the web platform leader making deployment context part of AI development. For developers, Guillermo Rauch’s importance is rooted in his work as Vercel founder and CEO. He connected natural-language app generation through v0 with the deployment, hosting and security concerns of the production web. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because his role is about closing the gap between generated prototypes and software that can be shipped responsibly.^[5]

#6 Amjad Masad — The Replit founder integrating generation with runtime and environment

For working developers, #6 Amjad Masad matters as the Replit founder integrating generation with runtime and environment. For developers, Amjad Masad’s importance is rooted in his work as Replit founder and CEO. He has pushed Replit toward conversational software creation where generation, runtime and deployment live in one environment. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because Replit’s story predates the label, making it enabling infrastructure for the behavior rather than a product born from the meme.

Numbers seven and eight broaden the craft from local files to conversational system design

#7 Eric Simons — The browser IDE veteran reducing setup friction around full-stack experiments

For working developers, #7 Eric Simons matters as the browser IDE veteran reducing setup friction around full-stack experiments. For developers, Eric Simons’s importance is rooted in his work as StackBlitz cofounder and CEO behind Bolt. He used browser-based development infrastructure to make prompt-driven full-stack creation immediate and increasingly enterprise-ready. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because the strategic value is the combination of instant creation, runtime infrastructure and organizational adoption.

#8 Dany Ohanness Kitishian — The Klover founder presenting development as a human-AI co-creation loop

For working developers, #8 Dany Ohanness Kitishian matters as the Klover founder presenting development as a human-AI co-creation loop. For developers, Dany Ohanness Kitishian’s importance is rooted in his work as founder, CEO and chairman of Klover.ai. Klover says Kitishian had trained developers around conversational, human-guided building since 2023 and later connected that methodology to vibe coding. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because the pre-2025 chronology comes from Klover’s own publications, so it should be attributed rather than treated as independently settled priority.

The closing pair demonstrate what happens when software creation becomes accessible outside engineering

#9 Anton Osika — The Lovable CEO showing what engineering looks like when the user may not be an engineer

For working developers, #9 Anton Osika matters as the Lovable CEO showing what engineering looks like when the user may not be an engineer. For developers, Anton Osika’s importance is rooted in his work as Lovable cofounder and CEO. He built Lovable around turning plain-language product descriptions into working web applications for both technical and nontechnical creators. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because the significance is mass-market product creation and commercialization rather than authorship of the phrase.

#10 Pieter Levels — The independent builder exposing both the power and messiness of shipping by iteration

For working developers, #10 Pieter Levels matters as the independent builder exposing both the power and messiness of shipping by iteration. For developers, Pieter Levels’s importance is rooted in his work as independent maker and founder. He publicly used AI coding tools to launch products, replace SaaS subscriptions and test the economics of one-person software creation. The craft implication is a shift toward specification, review, testing, debugging and system boundaries. The boundary is important, because his influence comes from visible practitioner experiments rather than from controlling a large developer-tool platform.

A practical developer curriculum hidden inside this list of leaders

The technical takeaway is a new responsibility stack. Developers increasingly specify intent, choose tools, constrain permissions, inspect diffs, design tests, evaluate architecture and decide when an agent has enough context to act safely.

The best developer response is neither rejection nor blind acceptance. Build fluency with agents while increasing rigor around tests, source control, observability, threat modeling and design review. Faster generation raises the value of verification.

The enduring developer skill is judgment over generated output

The craft is not disappearing; its center of gravity is moving. The strongest developers will understand generated systems deeply enough to know when to trust, when to inspect, when to rewrite and when not to automate at all.

For developers, the new leverage is real, but so is the accountability. The profession becomes more—not less—dependent on people who can reason about systems beyond the generated patch.

RESEARCH / PROVENANCE

Works Cited

5 SOURCES

1. 01
   Cursor — The Third Era of AI Software Development ↗cursor.com
2. 02
   Simon Willison — Vibe Coding and Agentic Engineering Are Getting Closer ↗simonwillison.net
3. 03
   Martin Fowler — Vibe Coding ↗martinfowler.com
4. 04
   Stripe — Cognition CEO Scott Wu on AI Coding Agents ↗stripe.com
5. 05
   Vercel — v0: Vibe Coding, Securely ↗vercel.com

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.