I like your definition of “vibe coding” better. Like, just hacking out some shitty c rogue-like, adding features as you feel like it, commenting out shit you don’t want to bother with.
That kind of coding is also where we get future self into trouble. Revisiting coding and having to figure out what the hell they were trying to do. They were just vibing, man. To read the code again, you have to rediscover that vibe, which may not be possible.
That describes all the coding I’ve written for decades now…even a side thing for work to automate stuff. I’ll be the first to admit I hack things until they work well enough and don’t legit code. Obviously coding isn’t my profession, that wouldn’t last long.
I like your definition of “vibe coding” better. Like, just hacking out some shitty c rogue-like, adding features as you feel like it, commenting out shit you don’t want to bother with.
Like “doodling” with code.
That kind of coding is also where we get future self into trouble. Revisiting coding and having to figure out what the hell they were trying to do. They were just vibing, man. To read the code again, you have to rediscover that vibe, which may not be possible.
I have quite a bit of code that requires a certain BAC/THC concentration to understand.
That’s gotta be how the Quake fast square root happened.
https://xkcd.com/323/
That basically describes all the code I wrote during college
That describes all the coding I’ve written for decades now…even a side thing for work to automate stuff. I’ll be the first to admit I hack things until they work well enough and don’t legit code. Obviously coding isn’t my profession, that wouldn’t last long.