I also built a Preview Pane Handler for 10-bit videos.
The installers (WIX) were vibe coded as well.
So was the product website and stripe integration. I created a bespoke license generation system on checkout.
I don’t think I wrote a single line of C++ code although the WIX installers and website did receive minimal manual adjustments.
Started with Claude but then at some point during development Codex got really good so I used only that.
It's not commercially successful (it's a side project), but still represents a complete project.
Database migrations and anything related to calculations have had a fair bit of hand holding. Beyond tests it writes I do still test by hand for confidence.
It’s coming up to a year of use. Claude Code credits has still not exceeded the cost of a paid product. I don’t count my time here because this doubles as keeping my technical side busy, and it’s been enjoyable.
I also built a solution for myself that was largely vibe coded. The underlying schema for inventories, batches, orders, cultures, etc was done in advance to help guide Claude along with documentation, but I'd guess 75 percent of the code is pure Claude.
It has worked really well for a while now. Since it's just me using it and I'm able to roll with issues it causes or verify outputs on the fly if I want to, it's totally fine not being super polished. It meaningfully increases my productivity by allowing me to manage things in a way that fits my mental model and business.
Like you, the cost of the project has been less than a subscription. And the subscriptions wouldn't even do what I needed.
I think the main issue is maintaining sterile conditions but its doable.
https://alexjacobs08.github.io/lobsters-graph/
(i built this in search of a lobste.rs invite if anyone willing and able sees this--email in my bio :)
I have rebuilt it a few times in agent mode while trying to get pmf. I used about 22B tokens this year
I cloned Paddle's NextJS starter kit[1] and incorporated my previous reporting code built with Observable Framework[2].
It actually took longer to get the website (domain, terms, privacy) approved by Paddle and my identity verified by its 3rd party than to vibe code the site with Claude Code.
My friend vibe coded the entire app to generate thumbnails for YouTube videos.
spocklet-pomodo.hf.space/
I created it as a single main.go with just a single main dependency (gorilla websockets iirc) and I think It's pretty successfull between me and my friends and I am not thinking of monetizing it ever
There is also https://spocklet-beta-pomodo.hf.space/ which has some more features to make it more user friendly that I got suggestion for so yeah
I made it out of complete frustration and the first prototype was built in <30 minutes but I guess I won't really take credit of it because I am just pleasant that I can now use such a software and perhaps other might too.
I don't know but I am very gloomy about AI mostly but prototyping in domains I don't know too much about to create a "just good enough" for my own use case is the only valid use case I find of it I guess.
Funny also how Loveable and the like are hiring engineers like crazy, yet think engineers are not needed anymore. Why not just vibecode Loveable itself? Oh wait I can tell you why.
It's telling that they will put their own applicants through a dozen rounds of stringent technical interviews, Leetcode exercises, use anti-AI assistance tools and pay their staff $500K or more, all for something they advertise as being easy to vibe code away.
Some types of programming benefit more from AI tooling than others. For example, prototyping seems to be the most fruitful area. Also, writing small utilities is much easier, to the extent that a two hour job would now take only a few minutes. That's where you get the multiplier posts from.
But working in a large codebase using proprietary libraries is not a solved problem for AI (yet).
It's just that the average engineer does not spend all of their time on things that can be sped up.
Speeding up 1% of your time by a factor 20 simply does not help very much. But for some roles, I'm sure that a 10% net increase in productivity is realistic.
I didnt join them because I dont really want to do all the work that comes with owning a business like the accounting. mostly the accounting. i also dont particularly want to be maintaining an extra couple of systems at present. there mught be vibe coding currently, but not vibe operations
they should have the thing up by june at their very slow rate of building with lovable, but theyre not people who would ever frequent HN.
I've never seen anything like it since the original days of the game "The Island of Dr. Brain" released in the early 90s.
https://github.com/rabfulton/ChatGTK
I'm sure the code can be critisized, but I'm happily using the application I wanted that did not exist having never programmed python in my life.
My experience so far has been if you possess both deep domain-specific experience and significant coding experience then these coding LLMs, and most notably Opus 4.5, are the greatest productivity booster in the world.
https://github.com/pannous/goo (1% handwritten go extensions)
I'm pretty familiar with the underlying stack, which helped a lot since I knew the pitfalls. But pretty much all of the code is written by an LLM.
I’ve done ~10 rides with it so far. Hoping I can convince my wife to use it and save myself $50 a month. That would be my most successful side project by a wide margin.
There are probably a lot of examples like this. Vibe coded software people made for themselves, and other people could use it if they wanted.
All of the code was reviewed by myself, and I’m a programmer, so not sure if that fits the description. I didn’t go through it with a fine-toothed comb, however, and 90% of the review was on my phone. I also did some non-vibed setup for hosting, db, email, etcetera.
To me vibe coding is not looking at any of the code at all, but the definition reads a little loose to me these days, especially on HN, as: did an LLM “type” most of the code or did you? Either way I don’t think the term or definition is a big deal and probably not worth splitting hairs over.
https://aldi-prices.lawruk.com/ https://github.com/jimlawruk/aldi-prices
It’s a suite of tools to navigate the Epstein files—it even made it into the news!
Here’s the HackerNews discussion: https://news.ycombinator.com/item?id=46339600
The "Methodology" that made it work: We moved from initial idea to production in four weekends while I maintained a full-time role. The key was moving past "chaotic vibes" and treating different LLMs like specialized team members: A) Strategic Layer (Gemini Pro): Used for architectural decisions (React/Vite, Node/Express, PostgreSQL/Prisma) and product prioritization.
B) Execution Layer (Claude Code): Used for heavy lifting—implementing the cron jobs, refactoring API patterns, and writing the test suite.
C) TDD as the Guardrail: We never "just coded." Every AI-generated feature followed a strict Test-Driven Development cycle using Vitest. If the tests didn't pass, the code didn't go to production.
The result is a stable system serving 200+ active users with a codebase that doesn't feel "schizophrenic" because we maintained strict cognitive boundaries and context documents for the AI to follow.
Tangents (https://tangents.chat) is an Angular/Nest/Postgres app for thinking-with-LLMs without losing the thread.
- Branch: select any span (user or assistant) and branch it into a tangent thread so the main thread stays coherent.
- Collector: collect spans across messages/threads into curated context, then prompt with it.
- You can inspect a "what the model will see" preview and keep a stored context-assembly manifest.
Vibe-coding aspect: about 600 commits and about 120k LOC (tests included) and I have not handwritten the implementation code. I do write specs/docs/checklists and I run tests/CI like normal.
What made it workable for something larger than a static page:
- Treat the model like a junior dev: explicit requirements plus acceptance criteria, thin slices, one change at a time.
- Keep "project truth" in versioned docs (design system plus interface spec) so the model does not drift.
- Enforce guardrails: types, lint, tests, and a strict definition of "done."
- The bottleneck is not generating code, it is preventing context/spec drift and keeping invariants stable across hundreds of changes.
If you define "vibe coding" as "I never look at the code," I do not think serious production apps fit that. But if you define it as "the LLM writes the code and you steer via specs/tests," it is possible to build something non-trivial.
Happy to answer specifics if anyone cares (workflow, tooling, what breaks first, etc.).
Its been very decent so far. Time will tell if the PMF is there for the MVP, but thats on the product, not the AI generated code slop.
FYI, this was more of a hobby horse + learning project than an "enterprise SaaS requiring SOC2 compliance." I am basically building a toy. So far, I have learned that you can ship code toys very quickly to test a market demand with an MVP.
sorcercode•3h ago
I was trying to test the theory if it's even possible to release something production grade with vibe coding. Wrote about the experience here https://kau.sh/blog/container-traffic-control/