CEO: "Why do we even employ 60 testers when our software have always been mostly bug-free on release and patched within a week?"
The QA who spent the last three weeks pressing the same button 4000 times in different situations:
Tales from mage support:
Mage: how can I help you
Lord: I was scrying local ladies when all the sudden my crystal ball started screaming that I have the pox and need to throw 100 gold under the bridge to cure it.
Mage: ... tell me you didn't throw gold under the bridge
Lord: ...
Mage: ...
Lord: so anyway you repollished the crystal last week so this is your fault. Fix it.
I mean yeah, commenter, that's the joke
I thought it was about antivaxxers at first.
Saw this when I was on reddit. People from all walks of life were commenting how this was relatable to their job/experiencs. Was pretty cool to see, you never think about some of their obscure jobs that are hella impactful
Actually, I sometimes wonder about it with my job.
I'm not doing the actual development. I get that's part of being a more senior engineer, but it makes me feel far less effective and skilled when all I do is communicate requirements, balance client needs vs business and infrastructure requirements, and review code and documents to ensure another team of engineers can support it.
But then, usually in some crisis scenario when shit is going down, the engineers responsible for the development become deer in the headlights. Instead of letting everyone panic, it's up to me to identify what broke (or what wasn't working to begin with) implement or communicate any workarounds, and get tickets/tests written up to be worked on/fixed and prioritized. It's those situations that remind me that a lot of our jobs aren't that flashy, but without them, nothing in the world would work.
Circle of Protection is working: Why do we pay you?
Circle of Protection fails: Why do we pay you?
Thats why you leave some low severity holes in your defenses on purpose.
I should tell Michael I appreciate his work
