Story of my work life: a feature I implemented in late 2024 has finally been tested by the embedded side. Who cannot make it work, and cannot send my code anything that even triggers any of the errors or warning about dodgy versions of that packet. I fear the spec they gave me has been changed significantly since I 'finished' my side (complete with test tool that sends those packets)
"Why hang out on the (#programming) forums then?"
This is something folks who don't #vibecode don't understand. Because they don't have the lived experience of vibecoding. All they know about it is from FEELS and other conservatives.
YOU STILL NEED TO BE A PROGRAMMER TO EFFECTIVELY VIBECODE!
After few decades of staring at the screen till your eyes bleed trying to figure out why "This function SHOULD work!", the romance of classical programming wears thin, since there is an alternative now. Sure some folks like pressing pins into their flesh. Good for them.
Its like enjoying the pure, liberating toil of digging trench with a spade. The satisfying crunch of the blade as it cuts the soil, the heft of a full tool as you throw it over your shoulder. The sweat.
Or you can sit in the air conditioned comfort of the digger, moving the joystick, digging at x10 the speed and going home without needing to take a shower just so you feel human.
Sure, diesel is cariciogenic, the treads crush everything and the digger is made in Asia with exploited labor. But there are no folks smashing the machine... Not since Brits hanged the leaders and deported the rest to Australia.
TL; DR: #Vibecoding is coding, but with powertools.
Its in the name.




