Surfaced kernel bugs with a stress test script that tries every option of every command in Toybox. It's the most aggressive test I could think up with the available software bits, and it's worked. Surfaced and fixed a pile of bugs.
4
Replies
0
Boosts
This is what I think is missing in most "vibe coding": standards. The kind of person who is drawn to vibe coding tends to be the kind of person who thinks test harnesses and documentation and iterative development are "old fashioned".
Me, I insist on things being tested thoroughly, put through exhaustive testing, aggressive bugfixing. Because I'm not interested in chasing clout, but in producing working software.
I assume by default that whatever the machine spits out is broken until proven otherwise.
The machine isn't special here: I assume that of my own code, and everyone else's too.
