Would you share the music app? Do you have a public repo or demo somewhere?

You didn't really describe it very much, so it's hard to say what it actually does. I'm interested in evaluating the quality of vibecoded projects people actually use.

▲

pdntspa 2 hours ago | parent [-]

At a later date, perhaps. I haven't messed with this project since I got employed and it was written over summer 2025, when the tooling for agentic development was a lot worse. (Very ADD here) There's also the open question of how best to package a python app that makes use of PyTorch and SciPy for distribution to nontechnical users. I want to solve that before I start putting this in other people's hands.

Careful with the term 'vibe coded', that does not characterize how I work.

▲

tovej an hour ago | parent [-]

Vibecoding is the term for building software with LLM tools. Did you do something different?

I'm just getting tired of hearing claims of incredible software being built with LLM-based tools, but when I ask to see them, I get nothing.

Your claim of 12-18 months for a windowed music metadata app seem weird. That seems like about a week with Dear ImGui and some file format reading libraries to me. Am I missing something?

	▲	pdntspa an hour ago \| parent [-]
		> Vibecoding is the term for building software with LLM tools without manual review and guidance. Coasting along purely on vibes. Hence the name. Agentic development is the middle ground where you're actively reviewing and architecting. Dear Imgui isn't a 'proper' windowing toolkit. It's immediate-mode, it doesn't use OS affordances. Its not WinForms or GTK or QT (though to be fair QT isn't quite native but its by far the closest) I never made any claims of 'incredible software'. I am building things that I need and want. I will give them to the world if I so choose and if they are good enough. And its not there yet. And considering that I have almost zero domain knowledge in the area of DSP or audio analysis, that I'd only have a couple hours a day to work on it at best (energy, motivation, and other factors notwithstanding), and the amount of learning it would take to get to the point where something like that would be "about a week" is where most of that 12-18 months goes. And yes the metadata and GUI parts are easy, but the code that generates the metadata that is good enough to perform with? Across every possible container/meta/audio format? That produces quality results on both beatport downloads and 96khz vinyl rips? I'm trying to build something to consolidate my original music library (hundreds of thousands of files) with divergent sublibraries on multiple (proprietary) DJ platforms. Basically cleaning up after 20 years of fucking around without a plan. That's hard.