Adventures in vibe coding

I’ve built a few apps now with the help of vibe coding, or AI-assisted coding as a lot of people prefer to call it.

CV.Gen is an app for putting together your CV with skills as tags. You get a clean export of your data in a resume format, but you can also export your data as JSON that you can use to render a different template. It’s all about keeping your data local first.

Chorus is a little different, because it requires people to collaborate with each other, so it needs a backend which I’m currently hosting. I quickly realized I’ll probably have a lot more ideas coming up, and if I had to spin up an app service for each one, I might end up with a really large bill 😀 So I decided to have one API to rule them all. I split the app between front and backend, but still vertically sliced.

The idea is, the more frontend apps I build, they’d just share the same backend event provider — at least until one of them gets traction. And because they’re backed by a file-based event store, moving it to a different app service will just be a matter of copying over the files under that app’s folder.

Chorus was the first app on it because choremonkey was already very integrated — I didn’t want to mess that up.

But the next app I built, Rent My Stuff, is using the same backend. So far it’s working great.

I have a few more app ideas lined up but I’ve just been tremendously tired lately. The AI vampire is definitely feasting.

For the latest on what I’m building, checkout http://itsybit.se