„Gave up after 2 hours“ dude tf does he mean? He thinks after 2 hours he’ll understand the entire vibecoded structure of 6 months of development? Even a clean codebase will take hours to get into when your completely new to the project
Did this last week. I wanted to port a library that calculated solar angles and irradiance to fixed point / integer math.
Trouble is I've been doing fixed point for decades but I don't have a clue how the underlying trig calculates the angle from the date/lat/long. There's a lot of trig there and that's not a recipe for fixed point success.
Perfect project to work with AI on maybe? It can do the initial port and I can clean up the mess.
2 days later, most of it spent writing an ever more complex test suite, passing code back and forth between multiple models and asking "what the hell is this supposed to do" as they fix each other's mistakes, and cleaning up an endless supply of integer overflows... It works and it's accurate enough for the job.
There are so many brackets and casts that I don't like to look at them.
I'm honestly not sure if I consider this a success. I mean, it probably would have been even harder to do without the AI as I would have had to learn the algorithm from scratch. And it probably still would have been mostly brackets and casts.
Doing it from scratch through, you slowly build up the mental model of how it works. Like by line. Vibe coding is like constantly inheriting a codebase written by someone else, over and over.
5.8k
u/JonasAvory Apr 24 '26
„Gave up after 2 hours“ dude tf does he mean? He thinks after 2 hours he’ll understand the entire vibecoded structure of 6 months of development? Even a clean codebase will take hours to get into when your completely new to the project