Ask HN: What are some impressive vibe coding projects?
11–20 of 52 posts
Re: Ask HN: What are some impressive vibe coding projects?
#12Re: Ask HN: What are some impressive vibe coding projects?
#13Earlier quoted context omitted.
I guess I just wanted to build my own, because my use case was really narrow and I knew it wouldn't take a lot of time. Guaranteed to not have any ads and trackers. Also needed an excuse to fully take github copilot's agentic coding for a spin.
Anki doesn't have any ads or trackers either btw.
Re: Ask HN: What are some impressive vibe coding projects?
#14Works quite well
Re: Ask HN: What are some impressive vibe coding projects?
#15Re: Ask HN: What are some impressive vibe coding projects?
#16A non-developer (but PM) friend of mine vibe-coded his own strength-training programming app that he uses daily. He pivoted from that to vibe-coding his own 2d game engine and 4x strategy game he's been working on.
He's effectively used vibe-coding to teach himself how to code and he brings me questions/problems as good as any working junior developer.
Re: Ask HN: What are some impressive vibe coding projects?
#17Re: Ask HN: What are some impressive vibe coding projects?
#18Interesting that this thread mostly consists of people sharing vibe-coded projects they themselves made, not people sharing other people’s projects that they’ve found useful. The latter would provide higher confidence that the project is actually impressive. It’s the IKEA effect for software.
https://www.robinsloan.com/notes/home-cooked-app/
As for sharing a tool that someone else has made that's useful, I don't think most people are advertising that the tools they've built are vibe-coded, so it would be hard to know what to share.
Re: Ask HN: What are some impressive vibe coding projects?
#19https://github.com/MARTYR-X-LTD/livi
Backend is Rust and Frontend is SwiftUI. At some point I'll make a Libadwaita frontend for a Linux release. Given my knowledge in Swift and Rust is pretty limited, it was an interesting project to learn the strenghts and limits of LLMs. I've learned quite a lot with it. Most useful lesson is that you might not necessarily need to know the specifics of a language, but you do have to have your common sense skills sound and clear, and how to code architecture a larger project, with refactors here and there, performance optimizations, multithreading, queue, cache and logs, and so on.
Maybe needless to say, but it wasn't easy. The produced code needed to be inspected constantly, and bugfixing, testing, handling edge cases required tons of prompting and guidance. The comparison features, such as pinch to zoom, keep the zoom and image positions while switching between the different generated images, handling exporting, all these features were loaded with intricacies. So far, glad that I was able to produce this.
As a fun fact, now that AVIFENC supports tune=iq, we don't have to mess with specific encoder settings and find the proper quality number anymore, but still, learned a lot from it