Sorry, no.
It’s inherently broken until you can prove how it works.
Bugs don’t just fix themselves; they lie in wait to ambush you.
Agreed, if this is you: it’s a very apparent skill issue.
Programming is not about typing until something works, it’s about problem solving.
It turns out to solve problems you need to understand the problem in order to determine it’s solution. Don’t understand it? It’s not solved yet.
Hence why everything “vibe-coded” is an even steamier pile of shit than most people think.
AI would like to have a word salad with you…
You don’t need to prove how it works; just that it does work.
If you don’t know how it do work, you don’t know for sure it do be working.
Unit tests.
Race conditions.
Yeah those are always fun!
Like, which runs faster, forced shutdown or Windows File Protection?..
It happens sometimes. Where I work, it’s not infrequent that some weird bug will come up (QA will find it or end users will report it or whatever) and we start looking into it, but never find the issue. The resolution ends up being “hopefully it was just a solar flare.” (By which we mean “hopefully it won’t ever happen again and we won’t have to invest more time in trying to figure out why it happened.”) And often it is.
Can confirm.
I’ve looked at some of my old code, and thought to myself “Fuck this looks like shit, maybe I should rewrite it from the ground up…”
And sure enough, my attempts to rewrite it never worked right. ☹️
So back to the original code base it was…
