One nice effect of vibecoding is having a proper description of the thing you want to have. I’m trying to develop a simple satellite tracking app and I didn’t even type a single prompt yet. There is stuff I want from Gpredict and Look4Sat, but I understand how difficult e.g. the radar view from Look4Sat is to develop (the thing you use to point your phone at a satellite) and how important it is to split the thing into libraries if I want a proper macOS app that doesn’t feel like running an iOS app in an emulator.

@turbocooler You are doing vibe coding wrong: you are thinking instead of vibing!

The other fun part is I feel like just learning Swift would be faster and more efficient. I don’t want this half-assed feel vibecoded apps have. Like they’re always in alpha and it turns out refining the code and fixing bugs is still a lot of work and you don’t even know or care how your code works. You can instantly tell a vibecoded app by these subtle bugs like some bad label alignment or navigation working strangely but sort of ok. The things you can tolerate which are likely the result of the weird way LLM “think”, so quite hard to fix using an LLM only.

I don’t really have time to learn Swift rn though.

@buherator haha, true!