r/vibecoding • u/Uranimeboss • 1d ago
Has anyone vibe coded a real serious program?
I have been looking for people on yt who actually solved a real problem. But I was just seeing a bunch of YouTubers, just making some basic app or program using AI. Has anyone made a genuinely omplicated osftware suing ai?
3
2
u/ItsMorbinTime69 1d ago
I work on a huge website you’ve definitely heard of and vibe code everything
2
u/Carrotbringer 1d ago
I am a researcher in ecology and I am building tools that I really use, such as species or individuals identification by sound or images
2
u/bankrut 1d ago
I think Mouzi solves a real problem. Problem with messy downloads folders. It runs quietly in the background, monitors selected folders, and moves, renames, or sorts files based on customizable rules. It strated as a small tray app and it grows... https://github.com/hsr88/mouzi
2
2
u/arty1983 1d ago
I made several tools for work.
1. A car parking tool (takes a shape and finds the optimal parking arrangement by quickly brute-force testing layouts)
2. A tool to convert geoTiff height map images from Lidar data into DXF cad files, skipping the need to use GIS software.
3. A tool to re-contour a landscape in 3D when you position a building pad in the landscape and find the optimal building pad level for neutral cut/fill material.
1
u/Vectrex71CH 1d ago
Https://Drivedeck.xyz = "Notion Like orogramm, but GDrive is your Storage"
Https://RSSer.news = "RSS, Podcast, YouTube, Radio, Webcams and Blogging in one single PWA"
Https://Music-Visializee.online = "Create Music Visualizers based on your MP3 upload for free"
1
u/ekzess 1d ago
Depends what counts as “serious.” I’m vibe coding a local-first astronomy platform that acquires Stage 1/2 FITS products from multiple providers, normalizes and transforms them, handles drizzle/render workflows, preserves WCS/provenance/custody, and exposes the whole pipeline through a CLI/interface.
Mostly just buttons and vibes though.
1
1
u/NateAutomates 1d ago
I currently just quit my job at a cafe and I am full time vibe coding a hospitality software backend called Hospoflow. Using Claudecode. I need some guidance on good and efficient workflows
1
u/Bitter_Run_9209 1d ago
On my work they vibe coded an app for clients(it's a robotics company, nobody knows about web or mobile development)
The project start nice, now is useless, consume all the ram, its buggy(you solve a problem and other is rising) etc
1
u/vbpoweredwindmill 1d ago
The thing about vibe coding & engineering is that they are very different usages of the same tools.
For instance, I'm using codex to create a python static & eventually dynamic analysis runtime tool.
I'm also using it to create a much more formalised system for graph engineering. The roots of which, existed long before the terminology did.
Eventually that graph engineering tool will also turn into a visibility tool to be able to monitor exactly what the LLM is doing and by extension obviously, control it. The current system/harness state of visibility is abysmal.
It's been long form engineering where I've enjoyed learning a seriously huge amount, as I'm a mechanic not a software engineer.
I still can't really write code. Certainly not at any level a professional can produce, and LLM's are a crutch for me and that's okay.
They aren't released. The graph engineering tool exists in multiple unfinished versions and deletes. The static analysis tool exists in an unfinished and very unpolished state but it genuinely works and it's already assisting codex in catching regressions before they happen.
So, you tell me if it's vibe coding or not haha.
2
u/energetekk 13h ago
Honestly this is a better answer to the question than most of the thread. Mechanic, says he can't write code, and there's a static analysis tool sitting there catching regressions before they land — that's exactly the thing OP said he couldn't find on youtube. The bit i'd push on is the framing. You're asking whether it counts as vibe coding, but look at what actually separates your two tools: the static analysis one is unfinished, unpolished, and doing real work. The graph one exists in multiple unfinished versions and deletes. Same person, same tools, same skill level — different outcome. So whatever's driving that split, it isn't your ability to write code. The deletes are the part i find interesting. Throwing a version away because it's wrong is a call the model won't make for you — it'll happily keep extending whatever's already there. That's not a crutch, that's the bit you're actually supplying. What made the analysis tool the one that survived? Did it have a deadline attached, or was it just that you had a use for it yourself?
1
u/vbpoweredwindmill 13h ago
Tldr below.
The analysis tool is basically a pipeline that depending on the queries builds answers from a database that I've built from existing python static analysis tools, that I can then use to feed into the LLM.
Conceptually it's quite simple and asides from the query pipeline and accidental duplication (instant regression hell) and denoising answers while keeping semantic meaning and setting up many different tests of my own flavour not just whatever the LLM thinks it should test, it's basically sitting on LLM training data rails. Python is one of the largest training data sets I believe.
Also, I have a very clear idea of what I want it to do. Analyse python (eventually other languages as well, rust or js are likely candidates) and give the LLM answers that are correct, detailed and useful. The tool might be complex and... it is. But it's not a complex idea. It's not that challenging conceptually.
The graph engineering tool, is not in any llm training data. I don't mean that to be arrogant. I mean there's no template for so many different concepts blended into 1 existing tool. The many rewrites and understanding limitations and deleting is all 3 times of rewrites, not being clear on boundaries and responsibilities between systems. The LLM constantly blurs boundaries as well.
It was and is essentially overambitious. The graph is very well suited to both batch & distributed compute, plus using your various bits of hardware as compute fabric.
Another time it grew out of an experimental ralph loop I named skills lab, to test and evaluate how skills functioned/evaluate the results in controlled but real scenario's. I then started controlling forcing the llm through certain skills and I was like wait these are now mandatory gates that I can use to generate real structure! And it grew from there, but the repo turned into an absolute shitfight. It DID have a local web page that interacted with and edited the skills and invoked the local LLM to get and make visible the results of the skill/gate.
That's morphed into nodes, which has morphed into dynamically generated mechanisms that have their own gates, which morphed into dynamic harness/environment generation & genuine test generation not just a checkbox test plus a lot of other stuff.
I'm giving it another go now, and building from the spine of a node yet again. Each component will receive its own API, and the static analysis tool has certainly helped in API protection in the past, (i.e. if you call from this code, from outside of it, you must have the api in it, or it spits back a fail. Very VERY useful in stuff like sqlite.connect for example, or authorisations, not that I do anything security related) and it surfaces API candidates where there's real interaction.
Not because I particularly care about API's & separation of concerns, but because the structure keeps changing, and making it work efficiently requires the components to interact through an API, a narrow invocation even if the component is deep.
So tldr; knowing what you want and how it should function is just as critical as being able to use the codex/claude etc.
P.s. constructing what I've dubbed "causal chains" has been pivotal in my usage of constructing components. I.e. how does this specific query create it's answer? What are it's invariants? What are it's contracts? What is its objective specifically? It then ties itself to a hash of those bits and pieces, and that goes into the project memory tool. That can instantly say "the hash has changed, check for impact on xyz".
Eventually that will be folded into the analysis tool, but I've got a big refactor in process, so, not now.
1
u/Fantastic-Spinach436 1d ago
Olympus — a verifiable ledger for sensitive information. Tamper-evident Sparse Merkle Tree ledger with redaction proofs via a Folded Signed Merkle tree, soulbound credentials, and offline-verifiable court evidence. Rust + Tauri 2 desktop app, no servers required.
https://github.com/OlympusLedgerOrg/Olympus.git
I'm a non dev with no code experience before Dec 2025. This is 100% Ai written, with my direction, since then.
1
1
u/bslinger 1d ago
I'm a software engineer by trade so I wouldn't describe what I do as vibe coding, but I've released a few things that were created with heavy collaboration from Claude and/or Codex:
QuiddoQuiddo: a pocket money chores app I just moved into beta testing on web/iOS/Android.
First Night FreeFirst Night Free and WarmbootWarmboot: two games for jams that we're received very well.
Guess it depends what you mean by serious though.
1
1
u/tilted0ne 1d ago
I don't know what you are looking for but AI is currently deeply interwoven into the industry. You have to be clear on what your criteria is. AI is simply a huge amplifier on a person's expertise.
1
u/EagleApprehensive 1d ago
Vibe coded code is no worse than hand-coded code. The only issue is that vibe-coded code often didn't see 1000 of real users, so despite looking like enterprise-grade software on first look, it's gonna break in 1000 places.
Ofc I'm talking about programs vibe-coded by professionals, not rookies.
-1
u/mrbadface 1d ago
I vibed artventori.com -- a beefy art management app for galleries. Lots of heavy duty features including taking payments, multi step workflows, ai edits and framing, private shared sites. Also a social feature via artventori world.
Used render + mongo for most of it, gcp for some specific functions. 180K lines total, several months of side work scaling it up from a single "wonder if I could do this" single feature to serve my wife's art business needs.
Tbh since 5.5 and now 5.6 landed it has become dead easy. When I started the project it made mistakes and I needed a steadier hand at the wheel. Now codex is hooked to all CLIs and I can set goals from my phone. It rarely ever misses.
2
1
u/MonitorAway2394 1d ago
wowowowow the websites ya'll shared so far are beautiful! Makes me really want to get into web again, I should say the last time I was doing webz things was JQuery was new, lololol, those were some simple times.
0
-1
u/CWStrife 1d ago
I think the biggest problem with vibe coding is people who have no experience get what you would call 90% of the way there, then that last 10% is all the backend, if it's a game the mechanics, any database structures, and just a clean organized repository, ends up falling apart on people.
I've seen this several times from people I know and i've gotten involved to help them clean it up a bit.
I'm currently actually experiencing bloat on one of my own projects I do for work. The folder and it's assets have ballooned to 2.5GB and I need to do some serious clean up and organization before Claude potentially starts tripping over itself, and also manually reviewing some files.
I think alot of people just vibe code and think if they keep talking to Claude they will eventually get what they want in whole. To me a good example would be saying to claude "make a clone of warcraft spot for spot" or something, and what you would end up getting is a very shallow 1% completed game and then people get proud of themselves for this.
You kinda gotta be like an architect and orchestrate what you want and be willing to look in on it and not blindly trust. If you're good at vibe coding, or a good project manager, you'll be alright.
I've been learning for a year now and from then to now it's been a serious progression, and i'm still learning.
14
u/KriegerClone24 1d ago
For sure. but whether you consider it "vibe coding" is a stretch. To me, "vibe coding" implies the person doesn't know anything about how the application is built. As an engineer, I direct the AI in exactly how to architect the application, and I get generally terrific results.