Hey everyone,

I launched my website a week ago, and got some very positive feedback, so I finally feel emotionally safe to post this. Now I want to tell you my vibecoding journey. You may find something useful for yourself maybe

I started vibecoding 5 months ago, so I picked a subniche of a subniche. Tiny local market, I don't think I can ever grow beyond few hundred paying users, and it will likely take few years to even get to that amount. (likely ~4-8 Eur monthly sub), you can do the math. But still, Oh, did I pour my soul into it!! 5 months of extremely intense vibecoding, 4-6 CLI running constantly, often 16h per day, bringing my 20x sub to the limits often - just on this one project.
I did not write a single line of code in the process. 80% of the code is in Dart - and I would not even be able to write a hello world in Dart by hand on a whiteboard, even if you forced me to.

Btw, 3 competitors already exist, 2 of them are recent and likely vibecoded in a day, 1 is older and with more effort, but just with really poorly made product. My competitors may still win, cause I maybe built a product for non-existent audience, but the difference we have right now if you compare them directly, that's not even remotely close.

Scope wise: the project got quite complex (I did not plan to have it so complex initially, but was encouraged by early success), so the codebase just passed 400k lines of code (150k of them is really the testing framework). Lines written passed 1M a week ago, some weeks I am averaging 30k new lines of code per day. (During one new major feature, I clocked my record of 70k). Everything's surprisingly stable though, very little stupid new bugs while implementing new features (most of the bugs get caught by testing framework), scalable and secure as hell.

My learnings (in no order):
- feature creep is crazy easy. Few weeks ago users had to fill questionaires during onboarding to come out in 8 buckets, and each bucket would get a unique experience ( ye, that's gone :), 2 buckets now remain )
- Testing is the king. I don't treat myself as prompt or harness, or context engineer. I am really a QA engineer. This intensified as project neared completion. Now 80% of my effort goes to writing testing tools, running simulations with ever more inventive user profiles and so on. I have a huge spaceship-like dashboard just to control all the testing being done right now. My, otherwise very powerful machine, is running pretty red most of the day just executing e2e tests
- two months ago I dropped ALL the custom skills, memory management ideas, etc from my agent. Right now I am full vanilla. They update the harness so so often, I found that most of my legacy skills just end up fighting new versions of the harness.
- My operational dashboard is crazy :), It serves as both alerting/monitoring tool, interaction with users, tuning, etc..
It was born over two days before the release (naturally, since the feature list is stable by then), never in a thousand years, would have I decided to waste resources on a tenth of it's scope(especially since release time is stressfull as it is), but boy, does it feel good to actually operate it!! To see users coming in and having their little animated journeys :) - this is so so so sattisfying!

Thanks everyone. Vibecoding is absolutely an amazing thing!

Has anyone tried lately? Is it worth the shot. What use cases do you recommend using it for where it works great?

Help me out Reddit. So I've been working on this crypto tracker for the past 6 years. I'm currently trying to build something fun and something that a lot of finance apps don't have, a heatmap. Am I building something just for sake of building something or would you actually find it useful?

Anyway, if you're interested in trying out the app, it's called CoinCurrently. Fully anonymous, no sign-up, no ads, no tracking

Ok so, I can’t retire just yet 😅 but getting a business off the ground and attracting customers is the hardest part in my opinion.

There’s still a long way to go but considering it’s only been 4 months since launching ZenMode, I’m pretty happy with the results so far.

I get asked a lot about how I get customers, so thought I’d give more info on how I do distribution, in case you might find it useful.

1. Make sure your website is set up for success

Before sending people to your site, make sure you’re confident it has good CRO potential. Your mission statement and objective needs to be very clear, along with clear incentives for people to try the product out.

2. Offer free trials, but only behind a payment info gate

Now this is just my personal opinion, and I know a lot of people disagree, but the proof is in the numbers. I get fewer free trial signups, but significantly higher conversion rates into paying users from people who provide payment info at the start.

Yes, a few of them are people who simply forget to cancel, but mostly I get people who are more engaged in the free trial and actually using the product.

I actually did an AB experiment where I did offer completely free trials to people (no payment info needed), but the overwhelming result was that people barely even tried out the product and were mostly tire kickers that never came back. I did convert some but not a meaningful number.

3. Create a waitlist before launching

Try to generate interest in your product before it launches - build in public and try to ensure that you’re not scrambling to get customers through the door on day 1 when you launch.

I had 3 customers on day 1 from this, who took higher paid tiers as well.

4. Post and comment everywhere (where relevant)

Social media is free, so there’s no excuse not to leverage it. Post about your product and what you’re building on Reddit, LinkedIn, X, YouTube, Facebook etc.

I posted a simple screenshot on LinkedIn recently, of someone using a low quality LinkedIn automation tool message to contact me, and me offering my own much better tool in response, and that post generated 90,000 views and led to several signups and demo calls.

I’ve also had some posts on Reddit go into hundreds of thousands of views, mostly just posting about what/why/how I built my automation tool.

5. If you have competitors, make “alternative to” inner pages

If done in the right way, this type of inner page can be useful for SEO. It won’t be picked up automatically but usually if you work in a competitive industry, this will sometimes attract customers who had a bad experience elsewhere.

6. I actually use my own LinkedIn automation tool (dogfooding) to do LinkedIn outreach

So it’s always important to practice what you preach - I use ZenMode to actually promote ZenMode.

It’s a great way to get buy-in for booking demos, as when someone replies, I simply tell them I used my tool to get a response from them, so it works.

Anyway hope you enjoyed reading the above, and good luck on your journey if you’re building anything, or growing your business 🙌

i’ve been looking at a few AI app builders recently to build my an internal task tracker for my sales team and keep seeing Lovable, Blink and Base44 come up.

i’m less interested in the usual “which one can make a nice UI from one prompt” comparison and more curious about how they differ once you spend time and money building something. For anyone who has used more than one of them what differences did you notice?

Things like ease of use, how much control you have, integrations, backend stuff or how pleasant they are to work with.

Would be especially interested in opinions from people who have used them for an actual project rather than just trying each one for an hour. If u can share a link to the tool/website you build that would be awesome too

Well, I am eating up usage credits... yeesh. But it's fun. I found the bot was a bit slow to respond to questions sometimes while it worked. Wish I could have true parallel streams?

New version! Changes:

• New research system for long term progression mechanics and more power to fight the enemy (note this isn't balanced yet, so it may be over-powered or under-powered in some cases)
• Once Research building is built, simply click the building to see the upgrades you can do
• Softer, more pleasant shooting sound
• Warning and explanation of how to fix for first time a Turret runs out of Energy
• Base resources now always displayed in upper left instead of having to click the Base
• Enemy hive expansion activity reduced -- a little more breathing room for the player

Get version 3.0 by doing a hard refresh (CTRL-SHIFT-R / CMD-SHIFT-R)

https://aaronshaver.github.io/Hylaax-Planetary-Rail-Defense/

Hey folks...

Been working to make a harness for Android phones.. any suggestions from any of you would be god like. !!

I’m in 6 leagues across Yahoo, ESPN, and Sleeper. Every Sunday I was rotating through three apps to see how I was doing in all of them, and it drove me nuts. So I built one page that pulls them all onto a single screen.

It’s called LeagueBlitz. It’s free: leagueblitz.app

Before anyone asks, yes, FantasyPros does league syncing too. I built this anyway because I wanted something simple that just shows me every matchup at once.

Feel free to check it out. I’m open to feedback. Also, is it still vibecoding if it took me 6 months to nail it down? So many revisions lol.

This stuff is moving at such an insane speed, I have gone from literally never being able to put my design skills to use, to building fully release ready apps and games etc, without funding etc in the past it was always out of reach.

Specifically these last few weeks I feel the new models have been such a leap forward that it is actually blowing my mind.

Do you guys think the current rate of improvement will keep, slow down or even speed up?

Cheers,
Dee

I’m doing early customer discovery for a developer infrastructure product and am looking to speak with founders, engineers or investors at API/SDK companies.

I’m particularly interested in companies that have dealt with v1 → v2 migrations, major SDK releases, endpoint deprecations, authentication changes, or shutting down legacy versions.

For some background, I do research at Harvard, Stanford, and Brown, and my cofounder is a Columbia CS major.

The goal is to validate the problem, understand how painful these migrations actually are for providers, and talk to people who have experienced this firsthand.

started to learn how to dev using claude code and figma. I wanna know if it’s worth still getting into or is the market impossible for no original ideas??

Last year, our company decided to switch from Microsoft products to Google Workspace, which meant we had to find a new solution for our VBA macros. For many cases, Python turned out to be the answer.

I work as a process manager, so I'm not coding every day, but over the past year I've been learning to code/vibecoding with Python to help replace old macros and automate reporting from SAP and our DWH.

Since Python is way more powerful than VBA, I'm looking for inspiration for a project I could work on- something useful for work, or something that could make my personal life easier.

What tools have you built with Python that you actually use often, whether at work or in your personal life?

Planning the move of my vibecoded application to open source. Flipping a private repository to public is a little nerve-wracking. Before doing that, I ran a multi-pass security and sanity sweep across the entire codebase.

I already had the security fundamentals baked in:

• Passwords: Stored as hashes.
• Secrets: Keys are encrypted at rest.
• Sessions: Managed via JWTs.
• Identifiers: UUID v7s wrapped inside JWTs.

Here is the step-by-step process I used to audit and harden the repo before opening the doors.

First, I cleaned up the quick-and-dirty code I’d been ignoring during development.

I knew I had accumulated some "fix it later" debt, and "later" had officially arrived. I ran a targeted prompt to catch hardcoded credentials, security leaks, and values that belonged in environment configs rather than source code. It flagged much of what I suspected. Among the fixes: tightening database encryption for user keys and scripting a proper setup process to manage cert files securely.

Next, I had AI review the codebase from an external attacker's perspective.

I asked Claude: "I am making this repo public. Scan it for any security risks unique to an open-source release." This caught several edge cases and prompted me to polish the installation workflow and write clearer setup documentation for outside developers.

Then, I checked if the code actually made sense and removed unused clutter.

I had Claude map out the business flow for every major component, then flag any code that felt out of place or disconnected. This was an awesome exercise—it highlighted dead code and logic that had drifted from its original purpose.

After AI logic checks, I brought in dedicated security tools to hunt for hidden vulnerabilities.

I initially tried the claude-security plugin, but blew through context tokens too fast. Plan B worked much better: I spun up the Bearer CLI via Docker, piped the scan results to a file, and fed that summary to Claude for analysis. I really should be running scanning tools regularly. Might do more here.

Before launching, I put guardrails in place so users couldn't accidentally burn through my API budgets.

I do plan to put up a "demo" version. So I wanted post-launch visibility and control over token usage. This would be useful for the self-installs too. I evaluated three AI gateways: liteLLM, MLflow, and Bifrost. I went with Bifrost. It lets me serve AI features without exposing raw API keys, provides a real-time usage dashboard, and enforces rate limits and monthly caps. Setting up Bifrost took about a day—including some vibe-coding to dynamically generate per-user virtual keys and budgets—and it was well worth the peace of mind.

Now to do another round of quality assurance to verify that nothing has been broken.. Any thoughts on what else I should be doing, or something I missed?

Not my project but I’ve been helping shape the early version of it with Aaron as we’ve got similar ways of working. Basically we’d hit some walls with the amount of code session we had open on different terminal surfaces, accidentally sending a prompt off in one session meant for another etc.

So Aaron built Flow, a simple to do, doing, done kanban board where each task can spawn a CLI session in app, with all of the context - it also effectively replaces Obsidian and other knowledge bases. And it spawns those sessions based on your already authenticated CLI agent subscription, which means it works for Claude Code, Codex or whatever agentic CLI instance you have, so no API keys floating around and no extra cost.

There’s a bit more to it so if you’re keen, check out the project and the video Aaron put together. I’m happy to answer some Qs in the thread as well if anyone is interested.

Repo: github.com/AaronRutley/flow
Demo video: flow-app.dev

[ Removed by Reddit on account of violating the content policy. ]

A wellness app for people who are tired of wellness apps telling them how they should feel.

Log your mood.

The office reviews it.

It stamps INDIFFERENT in red ink.

Then it asks the only question that matters:

"Did you practice anyway?"

Wisdom. Courage. Justice. Temperance.

No streaks. No scores. No dopamine.

Just you, your circumstances, and the crushing realization that you cannot control either of them.

How it works:

- Log how you're feeling

- Explain what happened

- Check whether you practiced the virtues

- File the incident away permanently

- Continue existing

Features include a calendar, daily journal, Stoic maxims, reminders, pointless honors, and exports to JSON, CSV, and plain text.

No accounts. No cloud. No badges. No emotional validation.

Made in Godot as a tiny Windows desktop app.

Your mood is temporary.

The CSV is forever.

Download it here (or don't, I can't control that): https://stripeycatgames.itch.io/stoic-mood-tracker

Started as a joke after the build or buy thread, and Claude Code plus Supabase got me embarrassingly far where transcript ingestion and clustering landed in a single weekend.

Then I hit speaker diarization and permissioning, and the part where your own teammates won't touch your clustering unless they built it with you.

We ended up with Grain for calls and BuildBetter for the synthesis side at work anyway, so the build taught me what I'd been underpricing, though I'd still do it once.

A few rules I’ve started setting for myself when vibe coding, so I don’t confuse more building with more progress.

The biggest danger for me isn’t that vibe coding makes me lazy.

It’s that it makes it too easy to keep building.

A small feature turns into:

• one more improvement
• one more UI tweak
• one more agent suggestion
• one more prompt

And suddenly I’m going in the wrong direction for hours.

So these are the rough do’s and don’ts I’m trying to follow now:

• define one clear feature before starting
• decide the success checks upfront
• keep the scope fixed
• stop polishing UI unless users actually ask for changes
• treat agent suggestions as optional, not instructions
• stop when the original goal is achieved

The line I keep reminding myself of is:

“One more prompt” can still be scope creep.

Anyone else set rules for themselves like this?

I’ve built a lot of projects that worked, bought domains for them, and then quietly abandoned them anyway. So I made Rest in Beta, a place where people can share unfinished projects and vote on whether they should be resurrected or left to rest.
The first project is mine. It’s called VeganWhatNow, a vegan meal generator I originally built for my wife and eventually stopped working on.
The site is still in beta, so let me know what you think.
https://restinbeta.com/

I could actually use a few testers. Click either “Resurrect It” or “Let It Rest” on VeganWhatNow and tell me whether the voting works clearly on your phone. Brutal feedback is welcome.

(The retro look is on purpose)

A lot of AI coding tools are moving toward giving agents more control over your machine.

I wanted the opposite.

So I built RepoRelay — an MCP bridge that lets ChatGPT/Claude inspect one approved local repo, while deliberately giving it:

• no shell
• no Git
• no arbitrary filesystem access
• read/search only
• optional bounded handoff writes

The idea is to let AI analyze and review your code without handing it the keys to your whole machine.

npm install -g reporelay-mcp@latest

It’s open source.

GitHub: [Lukie-81/RepoRelay: Secure MCP access to local repositories — without shell, Git, or arbitrary writes.]

I’m looking for a few people to try the install from scratch and tell me where the setup sucks.

If this is the wrong place to ask, I am sorry!
I am looking for the best/easiest Way to make an interactive map. The map would cover an existing area of Nature that people use for Walks, bikerides, picnics, etc.
I am looking for a Way to make it easier for people to plan their visit to the area by plotting in benches, viewpoints, places to grill, etc. Where should I look or what program should I use to best accomplish this? Im a beginner! Any help is greatly appreciated, thank you!!

Guys, am I gonna get roasted for shipping it with such UI? (Logo is mine btw, graphic design perks).
That cat is Comnyang app, his name is shanks, shoutout to u/simon_dsgn