People to follow
Vibe coding moves weekly. A tool launches on Tuesday, gets a big update on Friday, and by the next month everyone has a new favourite workflow. No book can keep up with that. People can.
This page is a short list of who to follow, read and listen to. It mixes builders who share their real numbers, the people making the tools, and a few careful sceptics. You want all three. Hype alone will get you an app with an open pantry.
On X
| Handle | Who | Why follow |
|---|---|---|
| @karpathy | Andrej Karpathy, AI researcher | Coined "vibe coding" in February 2025. Clear, thoughtful posts on where AI coding is going. |
| @levelsio | Pieter Levels, indie maker | Builds in public with Claude Code and shares revenue openly. A masterclass in shipping small. |
| @marc_louvion | Marc Lou, indie maker | Ships many small products and is honest about the wins and the failures. |
| @rileybrown_ai | Riley Brown | Friendly vibe-coding tutorials for non-developers. |
| @gregisenberg | Greg Isenberg | Startup ideas and AI-native business models. Good for the "what should I build?" question. |
| @mckaywrigley | Mckay Wrigley | Practical AI coding workflows. |
| @bcherny | Boris Cherny, Anthropic | Created Claude Code. Tips straight from the source. |
| @alexalbert__ | Alex Albert, Anthropic | Claude launches and prompting advice. |
| @claudeai | Claude | Official Claude product announcements. |
| @AnthropicAI | Anthropic | Official company news and research. |
| @amasad | Amjad Masad, Replit CEO | Where prompt-to-app tools are heading. |
| @antonosika | Anton Osika, Lovable co-founder | Lovable updates and the builder side of vibe coding. |
| @ericsimons40 | Eric Simons, StackBlitz CEO | Bolt.new news and launches. |
| @rauchg | Guillermo Rauch, Vercel CEO | Vercel, Next.js and v0. Where your app will live. |
| @kiwicopple | Paul Copplestone, Supabase CEO | Supabase news. Your pantry's landlord. |
| @swyx | swyx, Latent Space | AI engineering trends, explained well. |
| @simonw | Simon Willison | Careful, sceptical takes on LLM tools, especially security. Essential balance. |
| @mattppal | Matt Palmer | Credited with research behind the Lovable RLS vulnerability. A reminder to check your own app. |
| @catalinmpit | Catalin Pit | Developer humour, including the classic: vibe coding is easy, vibe debugging is the hard part. |
Handles change, accounts get renamed, and impersonators are common. This list is from late 2026. Before you follow anyone, open the profile and check it's the real person: look at the bio, the history and who else follows them.
A tip from Dev Uncle: don't follow everyone at once. Pick four or five, read them for a month, then adjust. A feed you can't keep up with is just noise.
Newsletters and blogs
- Latent Space: a newsletter and podcast on AI engineering. Deep, but readable once you've finished Part II.
- Simon Willison's blog: daily notes on LLM tools, with real experiments and honest caveats. His writing on prompt injection is worth reading before you ship anything with AI inside it.
Podcasts
- Latent Space: interviews with the people building AI tools and models.
Most of the people above also appear on podcasts regularly. Search their names in your podcast app.
Communities
- Indie Hackers' Vibe Coding hub: founders sharing what they built, what it earns and what went wrong.
- roadmap.sh vibe coding roadmap: a free, structured map of skills and tools. Good for seeing the whole landscape.
- r/vibecoding: the main Reddit community for vibe coders.
- r/ClaudeAI: Claude and Claude Code tips, prompts and problems.
- r/SideProject: show what you built and get early feedback.
- r/SaaS: the business side: pricing, churn, getting customers.
Communities are great for feedback and terrible for secrets. Never paste API keys, passwords or customer data into a public post, even in a screenshot.
Official docs
When a tutorial and the official docs disagree, trust the docs. They're updated when the tool changes. Tutorials often aren't.
- Claude docs: Claude, Claude Code, prompting guides.
- Supabase docs: auth, database, row-level security, storage.
- Stripe docs: payments, test mode, webhooks.
- Next.js docs: the framework QueueLess is built on.
A good habit: when Sous gives you an answer about a tool, ask it which page of the official docs says so. Then go and look.
One last thing
Following people is a fine way to learn. Building in public is a better one. Every success story in the case studies had an audience before launch day.
You don't need a big following to start. Post what you built today, what broke, and how you fixed it. In thirty days you'll have a record of the whole journey, and a few people who want to see what you ship next.