Michael is probably faster than a lot of these "fast hacker guys". He's trying to *very politely* explain that they should go learn to code. That would slow them down.
Like, if it's a website, people should see something other than "DatabaseClosedError: UpgradeError Not yet support for changing primary key" when they click on the link. 🤦♀️
Ultimately I agree with you. I have some weird tendency to test the living shit out of stuff I write. I think it's just many years of devops being on the receiving end of bugs. I even used to make company wide rules like no releases on Fridays and stuff like that.
Probably from an outside perspective it seems like I'm slow. But I don't like bugs and am very good at finding them after all these years of paratrooping other people's code and being tethered to a pager.
I don't know why more testing isn't done. I can always name off things that can help, recommend process or dev environment improvements, train eng teams how to read their own logs, but at the end of the day it's a life long mystery for me..
You're the only person who has ever paid me to test out their stuff. That's why I subscribed and am happy to pay you. 😅
Literally a core quality measure.
I think a lot of people don't get *why* I consider it a quality measure. It says
1) I expect my stuff to work.
2) I have bad feels when it doesn't work.
3) I know checking to make sure it works is also work.
4) People should be paid for their work.
5) Thank you for working for me.
I don't actually burn out of testing or reporting bugs. I spent 5 years doing that all day, every day.
I burn out on the attitude of the person I'm testing and reporting for.
