MAHDOOD
· 6h
When I was a kid, my friends came over with their family to spend the day with my family. My friend had an essay that was due so I was asked to open the file on the computer using his floppy disk so h...
In the same way that authors are better off having someone else proof-read/edit their works, nearly every dev is the worst person to QA their code.
In the commercial world, a large part of being a QA engineer is the psychology of informing a dev that their code isn't perfect.
In the non-commercial world, many devs prefer to ignore any (or all) criticisms, aside from the program crashing, or complete failure of some basic functionality. Even then, I've seen where devs say they don't care about the user. I'm baffled why those devs publish to begin with.
Even the devs that do care about making a polished product, they often can't put themselves in the position of ignorance and lofty expectations that many users will have. In fact, most people are not good about putting themselves in someone else's shoes. A vast majority of people cannot overcome their own bias.
It really takes someone with a good imagination to create proper tests, outside of the rote panel of test cases. The best replacement to that is "the actual user", but when devs ignore a message that translates to "more work, and not really fun work", they'll tend to turn a blind eye.