There's a new feeling in software right now, and it's a good one. You open Claude, or Cursor, or v0, type out an idea in plain English ("build me a habit tracker with streaks and a leaderboard"), and twenty minutes later there's a real, clickable app sitting on your screen. No bootcamp. No CS degree. No permission slip required from anyone.
People are calling it "vibe coding," and honestly, the name fits better than most industry buzzwords do. You're not architecting a system or debugging a stack trace at 1am. You're vibing: describing what you want, watching the AI build it, tweaking your instructions, watching it build some more. It feels less like traditional engineering and more like directing a fast, literal collaborator. You say "make the button pop more" and it pops more. You say "add a login screen" and there's a login screen. It's addictive in the way any fast feedback loop is addictive.
And the stuff people are building right now is genuinely wild. Solo founders are shipping full MVPs in a single weekend, the kind of build that used to take a small team a month and a real budget. One founder we came across built a working waitlist app, complete with referral tracking and email automation, in an afternoon between other meetings, then had it live and collecting signups by dinner.
Designers with zero backend experience are standing up working products end to end, database included, without touching a terminal command they didn't copy and paste. We've seen a designer go from a Figma mockup to a functioning booking app with real-time availability in a single sitting, something that would have needed a developer handoff and a two-week sprint not long ago.
Non-technical operators are automating entire workflows they used to pay outside agencies thousands of dollars a month to maintain: invoice generation, customer follow-ups, internal dashboards that pull from three different tools and finally talk to each other. Marketing teams are prototyping internal tools between meetings instead of filing a ticket and waiting on the dev team's backlog. Product managers are turning Figma comments and Slack threads into working demos before the standup even ends, walking into the room with something clickable instead of a slide.
None of these people would have called themselves builders a year ago. Now they've got something live, something they made, and a story to tell about it.
The barrier to "I built this" has never been lower, and the energy around it is contagious. Scroll through Twitter or LinkedIn on any given day and you'll find screen recordings of people watching their first app come to life in real time, narrating it like they're unwrapping a gift. There's a real sense of a floodgate opening. People who spent years assuming "I'm not technical enough" are suddenly building things they're proud of, and sharing that pride loudly and publicly.
We get it. We've felt it too. There's a genuine rush the first time an AI tool takes a sentence you typed on your phone and turns it into working, deployable software. It's fast, it's fun, and for a moment it makes you feel like you've been handed superpowers that used to require a four-year degree and a signing bonus.
That rush is real, and it deserves to be celebrated rather than immediately picked apart. Too much commentary on AI tools right now jumps straight to the skepticism: the "yeah but is it actually good code" takes, the hot takes about technical debt, the doom-posting about what happens when it breaks. All of that has its place, and we'll get there. Just not this week.
This week, we just want to sit in the feeling for a second, because it's a good one and it's worth noticing. If you've been vibe coding, we want to hear what you built. Tag us, send us a link, show us the thing you made that you didn't think you could make. If you haven't tried it yet, consider this your sign. Pick a small, silly, fun idea and see what happens when you just describe it out loud to an AI tool. You'll be surprised how far vibes alone can take you.
But you probably knew a "but" was coming, because there always is one. Vibe coding has a honeymoon phase for a reason. Every relationship has one, and every relationship eventually moves past it. The first version of anything is always the easy part: the blank page, the exciting build, the dopamine hit of watching something appear where there was nothing before. The harder question is what happens next. What happens when the project grows past a weekend hack and into something people actually rely on? What happens when the vibes-only approach hits a wall of real users, real edge cases, and real stakes?
That's exactly where next week's post picks up. For now, though: enjoy the rush. You earned it, and there's nothing wrong with celebrating the fact that building software just got radically more accessible to more people than at any other point in the history of the industry.