I've been vibe-coding a Plex music player app for MacOS and iOS. (I don't like PlexAmp) I've got to the point where they are the apps I use for listening to music. But they are really just in an alpha/beta state and I'm having a pretty hard time getting past that. The last few weeks have felt like I'm playing wack-a-mole with bugs and issues. It's definitely not at the point others will be willing to use it as their daily app. I'm having to decide now if I keep wanting to put time into it. The vibe-coding isn't as fun when you're just fixing bugs.

▲

peteforde 8 hours ago | parent [-]

Genuinely curious: are you actually vibe coding (as in not writing or looking at the code) or are you pair programming with a current model (eg. Sonnet or Opus) using plan -> agent -> debug loops in something like Cursor?

▲

patchorang 7 hours ago | parent [-]

I haven’t written or looked at a single line of code. I do use plan though, and have a technical background but haven’t meaningfully coded in 15 years

	▲	peteforde 5 minutes ago \| parent [-]
		I think it's great that you've gotten back into coding, even if you're hands-off for the time being. However, I strongly urge you to leave not touching the code behind as a silly self-inflicted constraint. It is pretty much guaranteed to only get you to about 40% of the way there for anything more than a quick prototype. Hardcore cyclists can confidently ride without touching their handlebars, but nobody is talking about getting their handlebars removed. It's just a goofy thing that you might try for a few seconds now and then on a lark. That's vibe coding.