I vibe coded 30+ apps in 2 years. 6 are still in production with real users. Here's what I learned. : vibecodingjump to contentmy subreddits<br>edit subscriptions<br>popular<br>-all<br>-users<br>| AskReddit<br>-pics<br>-funny<br>-movies<br>-gaming<br>-worldnews<br>-news<br>-todayilearned<br>-nottheonion<br>-explainlikeimfive<br>-mildlyinteresting<br>-DIY<br>-videos<br>-OldSchoolCool<br>-europe<br>-TwoXChromosomes<br>-tifu<br>-Music<br>-books<br>-LifeProTips<br>-dataisbeautiful<br>-aww<br>-science<br>-space<br>-Showerthoughts<br>-askscience<br>-Jokes<br>-Art<br>-IAmA<br>-Futurology<br>-sports<br>-UpliftingNews<br>-food<br>-nosleep<br>-creepy<br>-history<br>-gifs<br>-InternetIsBeautiful<br>-GetMotivated<br>-gadgets<br>-announcements<br>-de_IAmA<br>-WritingPrompts<br>-philosophy<br>-Documentaries<br>-Bundesliga<br>-EarthPorn<br>-photoshopbattles<br>-listentothis<br>-blog

more "

reddit.com vibecodingcomments

Want to join? Log in or sign up in seconds.

limit my search to r/vibecodinguse the following search parameters to narrow your results:<br>subreddit:subredditfind submissions in "subreddit"author:usernamefind submissions by "username"site:example.comfind submissions from "example.com"url:textsearch for "text" in urlselftext:textsearch for "text" in self post contentsself:yes (or self:no)include (or exclude) self postsnsfw:yes (or nsfw:no)include (or exclude) results marked as NSFWe.g. subreddit:aww site:imgur.com dog<br>see the search faq for details.

advanced search: by author, subreddit...

this post was submitted on 21 Jul 2026<br>2 points (100% upvoted)<br>shortlink:

Submit a new link

Submit a new text post

vibecoding<br>joinleaveA community of software creators experimenting with AI "vibe coding", an technique defined by Andrej Karpathy as when, "you fully give in to the vibes, embrace exponentials, and forget that the code even exists."

a community for 1 year

MODERATORS

message the mods

89 &middot; 49 comments

Come hang on the official r/vibecoding Discord 🤙<br>351 &middot; 168 comments<br>0:19

I built a tool that tells you who already tried your startup idea, and how they died<br>&middot; 6 comments

What do you think his reaction would be? 😂😂<br>1392 &middot; 192 comments

You used AI? That's not real programming<br>25 &middot; 2 comments

I told codex to move a button 4px. My ai bro rewrote the entire layout.<br>535 &middot; 59 comments

Go Kimi Go 🚀🚀🚀<br>12 &middot; 7 comments<br>Vibe coding has genuinely made my life better. And more fun!<br>214 &middot; 34 comments

JSON Born, the hero we all forgot how to write<br>61 &middot; 102 comments<br>1:19

100% Free Kanban Board - no paywalls, no signups, no subscriptions<br>19 &middot; 27 comments

Google dropped 3 new Gemini models today and somehow still no Gemini 3.5 Pro

Welcome to Reddit,<br>the front page of the internet.<br>Become a Redditorand join one of thousands of communities.

&times;

&bull;<br>&bull;<br>&bull;

I vibe coded 30+ apps in 2 years. 6 are still in production with real users. Here's what I learned. (self.vibecoding)<br>submitted 9 minutes ago by SweatyCompetition343

I've vibe coded more than 30 apps over the last 2 years, and more than 6 are still in production with real users. Here are my takeaways and advice:

1. Build reusable bricks. When you vibe code an app, think about the "bricks" that could be used elsewhere, and tell your agent to develop them in a stateless way — or at least not tightly coupled to that specific app. It adds some complexity at the beginning, but hell, you'll be happy when you reuse them for the 5th time. Examples from my own projects: image resizing/optimization, UI media generation, etc.

2. Pick a stack and stick to it. Deploy all your apps to the same place — Cloudflare, your own VPS, whatever. Juggling many providers will make you struggle with updates, accounts, billing, and all that noise.

3. Note your bottlenecks — they WILL repeat. Whatever made you struggle on one app has a pattern of coming back on the next one. Write it down. Example: I kept running out of disk space on my dev servers — not S3 or anything fancy, just space inside the servers — because I'd forget to clean up unnecessary files on my workers. Suddenly you're a sysadmin instead of a vibe coder. Solution: vibe code a cleanup worker for every app and forget about it.

4. Centralize secrets, configs, and env variables. Hell yeah. There are so many open source solutions for this. Just be aware of the security vs. centralization tradeoff.

5. Have a unified way to resume any app where you left off. When you have multiple vibe coded apps, you need one place to pick up dev exactly where you stopped — with the agent's memory and context for each app. This is why I prefer developing my apps in the cloud. And yes, there are solutions for that too.

6. Build a central brain for ALL your projects. This ties into the last point, but hell — centralize everything you know about your projects in one place. You WILL forget a lot of things. You'll even forget which technology you used for which project for which client. Tools like Obsidian on desktop are great for this, and there are cloud options too.

2 comments<br>share<br>save<br>hide<br>report

all 2...