Key takeaways
- Start with one free course: Vibe Coding 101 with Replit (1h34m, beginner) for non-engineers, or Cursor Learn for anyone who already writes some code.
- Watch real workflows before you buy anything. How I AI (129K subscribers) shows one practical build per episode, and Riley Brown (315K subscribers) makes tutorials for people who do not code for a living.
- Read Simon Willison's March 2025 essay before you write a policy. His narrower definition, building software with an LLM without reviewing the code, is the line between a prototype and something your engineers must own.
- Use vibe coding to decide whether something is worth building. Our Labs write-up documents a working app shipped in about 14 hours for US$84.31, and a bug that 90 minutes of prompting could not fix took four minutes once someone read the code.
- Once a prototype needs to survive real users, move the team to the practices on our agentic engineering resources page.
Which resources are worth your time for learning vibe coding?
Ranked within each group by how much a technology leader gets out of it. "Checked" says where each number came from and when.
Creators and shows
-
129K subscribers · weekly episodes on Lenny's Podcast network
For: Product managers, designers and executives who want to see realistic vibe coding workflows end to end.
Each episode is a live screen share of one practical workflow with immediately reusable tips, and many feature non-engineers building real tools with AI. Vo builds ChatPRD and launched the show on Lenny's Podcast network in April 2025. It is the best source of realistic examples to show a leadership team that has not tried these tools.
Checked: YouTube channel page (subscribers, description, sponsorship email in video description); host's launch post on chatprd.ai, 19 Nov 2026
-
315K subscribers · tutorials, weekly news, A New Vibe Podcast
For: Non-engineers and founders building their first apps with AI tools.
Brown makes build-along tutorials plus weekly updates on what changed in OpenAI, Anthropic, Google and xAI tools and whether you should switch. The videos are quick and upbeat, which suits a first prototype. Pair them with a review habit before anything touches real users or real data.
Checked: YouTube channel page (sponsorship email in channel description), 19 Nov 2026
-
154K+ Substack subscribers · YouTube 118K subscribers
For: Product managers who want to prototype without waiting for an engineering sprint.
Yang led product at Roblox, Reddit, Amazon (Twitch) and Meta and now writes short, practical AI tutorials, including '12 Rules to Vibe Code Without Frustration' and step-by-step builds with Bolt, Cursor and Claude Code. Some tutorials sit behind the paid tier. His YouTube channel has playlists on Codex and Claude Code for those who prefer video.
Checked: Substack home page (154,000+ subscribers) and About page; YouTube channel page, 19 Nov 2026
-
1.77M subscribers · long-form explainers
For: Leaders and non-engineers who want to understand the models behind vibe coding tools.
Karpathy coined 'vibe coding' in a February 2025 post on X, and his channel is the best free grounding in what the models underneath these tools are doing. 'Deep Dive into LLMs like ChatGPT' and the Neural Networks: Zero to Hero playlist explain why an LLM can write plausible code that is still wrong. One general-audience video is enough before you judge a vibe-coded prototype.
Checked: YouTube channel page, 19 Nov 2026; coinage per his X post as cited in our Labs article and Simon Willison's March 2025 essay
-
744K subscribers · The Startup Ideas Podcast
For: Founders and innovation leads who want to see what solo builders now ship with AI tools.
The channel carries Isenberg's Startup Ideas Podcast and tutorials on using AI to build and grow a startup, with frequent episodes on shipping apps and agents quickly. It is founder-oriented and idea-heavy, light on engineering detail. Use it for a sense of what is possible, then use the courses below for how.
Checked: YouTube channel page, 19 Nov 2026
-
Free · 104 posts tagged vibe-coding
For: Engineering leaders writing a policy on where vibe coding is allowed.
Start with his March 2025 essay 'Not all AI-assisted programming is vibe coding (but vibe coding rocks)', which argues the term should mean building software with an LLM without reviewing the code it writes. The rest of the tag is a running log of experiments, tools and failures. It gives you precise language for the line between a prototype and production code.
Checked: Creator site (essay dated 19 Mar 2025; tag page count), 19 Nov 2026
-
Newsletter, podcast and apps · YouTube 51.7K subscribers
For: Teams that have outgrown pure vibe coding and want a more disciplined method.
Every writes about how its own small team builds software with AI agents, including its 'compound engineering' method and candid pieces such as 'I Vibe Coded a Security Risk'. That makes it the natural bridge between vibe coding and agentic engineering. Part of the archive requires a paid subscription.
Checked: Publisher site and YouTube channel page, 19 Nov 2026
Official guides from the tool makers
-
Official course · 13 lessons in two modules
For: Developers and technical PMs moving from chat prompts to agent-assisted coding.
Cursor's official course explains how models work, hallucination, tokens and pricing, context, tool calling and agents, then covers working with coding agents: understanding a codebase, building features, fixing bugs, and reviewing and testing code. The examples use Cursor, but the course says the patterns apply to any AI model or product. It is the best single primer for someone who already writes a little code.
Checked: Vendor course page, 19 Nov 2026; price not stated, lessons readable without sign-in
-
Free official documentation
For: Product, design and operations staff building first internal apps in Lovable.
Lovable's own guide to prompting its app builder, including working in Plan mode and asking the tool to question you before it writes code. It is the right primer for non-engineers on Lovable, and I'd expect most of the habits to carry over to Bolt, Replit and v0.
Checked: Vendor documentation, 19 Nov 2026
Courses
-
Free · 1h34m · 7 video lessons · beginner
For: Non-engineers who want one structured, short introduction.
Taught by Replit's Michele Catasta and Matt Palmer, the course builds two apps, a website performance analyzer and a voting app, with Replit's agent, and teaches product requirement documents, wireframes and prompting along the way. At under two hours it is the cheapest structured start on this list. A certificate of completion needs DeepLearning.AI's paid PRO plan.
Checked: Course page (updated 17 Jul 2026), 19 Nov 2026
-
Free · self-paced
For: Vibe coders moving to a terminal agent on a real repository.
Anthropic's free introduction to using Claude Code in a daily development workflow, followed by Claude Code in Action for long, hands-off sessions using plan mode, hooks and verification. It fits the moment a prototype starts to matter and someone needs to steer the agent instead of accepting whatever it writes. Engineers already fluent in Claude Code can skip straight to the second course.
Checked: Course pages (marked FREE), 19 Nov 2026
Book
-
Book · published 21 Oct 2025 · paperback, ebook, audiobook
For: CTOs and VPs of Engineering deciding how far to let AI-written code into production.
Subtitled 'Building Production-Grade Software With GenAI, Chat, Agents, and Beyond', with a foreword by Anthropic CEO Dario Amodei. Its production-grade framing makes it the one book here to hand a sceptical engineering leadership team. Read it alongside the shorter free resources, since tools have moved since publication.
Checked: Publisher page, 19 Nov 2026; price varies by retailer
Communities and events
-
Meetups, cafes, hackathons and workshops worldwide · forum
For: Teams who want to see how other companies organise AI-assisted building.
Cursor's community programme runs meetups, Cafe Cursor sessions, hackathons and workshops in cities from Dublin and Paris to Bangkok and Colombo, and its forum at forum.cursor.com is active. A local meetup is the cheapest way to compare notes with other teams. Check the page for a city near your office.
Checked: Vendor community page, 19 Nov 2026
What is vibe coding, and when is it the right tool?
Vibe coding is right for prototypes and throwaway tools where failure is cheap and the problem is well known. Karpathy's original description was to 'fully give in to the vibes' and forget the code exists. Simon Willison narrowed it to building software with an LLM without reviewing the code it writes; read and test everything, and you are doing ordinary AI-assisted development.
Our vibe coding Labs test shows both sides. The build produced about 6,200 lines in roughly 14 hours for US$84.31, and only about 340 of those lines were read. Common patterns such as forms, CRUD screens, SQLite schemas and deploy configs came out fast and correct. A timezone offset applied twice survived 90 minutes of prompting and took four minutes to fix once the file was read.
That sets the decision rule. Use vibe coding to find out whether something is worth building, and keep it away from systems that handle sensitive data, money or long-term maintenance. The 2025 Stack Overflow survey cited in that piece found 84% of developers use or plan to use AI tools while 46% distrust their output, which is a fair summary of where most teams sit.
Which vibe coding resources fit which person?
Pick by role, because the gap between a curious executive and a staff engineer is wide. Non-engineers should start with Vibe Coding 101 with Replit or Lovable's prompting guide, then watch Riley Brown for build-alongs. Product managers get the most from Peter Yang and How I AI, since both show people in product roles shipping real tools.
Engineers should take Cursor Learn or Claude Code 101 and read Simon Willison's essay, which will save them from arguing about definitions. Leaders need the least hands-on time: one Karpathy explainer, the Gene Kim and Steve Yegge book, and a few Every pieces will give enough context to set policy. Founders and innovation teams looking for ideas can add Greg Isenberg.
Whoever the learner is, insist they build something. Every resource here is more useful as a companion to a small real project than as a course to finish, and the first broken build teaches more than the first tutorial.
How should a company let non-engineers vibe code safely?
Give vibe coders a sandbox and a promotion path, and most of the risk goes away. A sandbox means a separate workspace with no production credentials, synthetic or public data only, and spend limits on the AI tools. A promotion path means a clear point at which an app that people start relying on goes to engineering for review, tests and ownership.
Write down the data rule first. Customer data, credentials and payment flows stay out of vibe-coded apps until an engineer has read the code, which is the gap Every's 'I Vibe Coded a Security Risk' describes: an app that worked and that nobody had checked for safety. Our AI code review benchmark covers tools that can help at the promotion step, though they do not replace a human reviewer.
Count the cost too. Seat licences are cheap compared with the engineering time spent rescuing an unowned app a year later. Keep a simple register of what has been built, by whom and on what data, and review it each quarter.
How long does it take to learn vibe coding, and what does it cost?
I'd expect a non-engineer to build a useful first prototype within a week of part-time effort using the resources here. The Replit course takes under two hours, Lovable's guide about an hour, and the rest of the week goes on building and breaking something small. Engineers pick up the tools faster and find the habit of letting go of the code harder, which is the part worth practising on purpose.
Most of the learning is free; the paid parts are tool subscriptions and usage. Check current plan prices on each vendor's site before you approve seats, because they change often and usage overages add up once people build daily. The Labs build described above cost US$84.31 for one weekend, a useful order-of-magnitude figure for a single prototype.
Leaders need less time than either group: an evening with one Karpathy explainer and a How I AI episode, then an afternoon building something small yourself. Having tried the tools first-hand makes the policy conversation with your engineers much shorter, and it makes you a better judge of the demos your teams will bring you.
When should a team move from vibe coding to agentic engineering?
Move the moment a vibe-coded app gets real users, real data or a second maintainer. At that point the code has to be read, tested and owned, and the skills change from prompting to scoping, verification and review. Our agentic engineering resources page lists where to learn those.
The bridge is usually a written spec. Our spec-driven development test shows what changes when an agent works from a spec instead of a stream of prompts, and Every's compound engineering pieces describe a similar loop. Claude Code in Action and Cursor Learn's reviewing and testing lessons cover the mechanics.
Plan for the cost curve as well. Usage grows quickly once a team works with agents daily, and our 90-day Claude Code cost log is a realistic reference for budgeting heavy users.
Listed here, or should be?
If your entry is out of date or you think something belongs on this list, email [email protected]. Entries are editorial and free. A featured, labelled Sponsored slot is available through vendor listings.
Related questions
- What happened when we shipped a production app with vibe coding?
- What are the best resources to learn agentic engineering?
- How do AI coding agents compare without a feature table?
- Does spec-driven development with AI agents work on a real build?
- Which AI YouTube channels are worth following?
- Where should a leader start with AI education?
More from AI Education
- AI Education: where technology leaders learn AI in 2027
- AI conferences
- AI YouTube channels
- AI accounts on X
- AI newsletters
- AI podcasts for executives
- AI voices on LinkedIn for executives
- AI books for technology leaders
- AI peer communities for executives
- AI courses and university programs
- Agentic engineering resources
- AI tool stack for CTOs
- The full AI Education hub on We The Flywheel, with niche lists for every role