[leftouterjoins]

I have been doing full stack web dev since 2003 and iOS apps since 2008. I do not write code anymore. At my day job I don't think I get more done over time because the code is rarely ever the bottleneck at that place. I do have more time to experiment and try things and say yes more to asks from colleagues.

Outside of work, I have just launched an iOS app I've wanted to build but has been outside my current skillset. I was able to "vibecode" this app in about 4-5 months.

The application has a tiny bit of moat because it involves a ML model (also vibecoded) trained on my own data set.

When I say vibecoded, I never reviewed or read code in detail. I really only ever saw snippets claude code shows here and there. I asked a lot of questions, much more than asking it to make changes. I only gave it high-level architectural guidance like "use MVVC", etc. I did a lot of manual testing and reading logs.

I won't name the app out of fear of shilling my vibeslop, or whatever, check my profile for the domain in an email address if you want to know more.

[_vlie]

I think this is exactly the kind of example I wanted to see, so thank you for sharing. I was thinking about it yesterday and realized that it might actually be worth trying to switch my current project entirely to “vibe development.” That said, I still worry a bit that AI might change the structure or expand the code when all I really want is to tweak a single line or a few expressions—but I’m sure there’s a way to handle that.