Use cases are hypothetical scenarios worth getting mad over. They are THE things we should give a shit about. When somebody on my team suggests something that's user-hostile in 1% of cases because they don't give a shit, I'm not going to just say, "well, I better not have negative emotions". That's how we get the garbage world.

If you want to do a good job, definitely do not get mad over use cases.

Devs are more like Spock, not The Hulk.

We work better when we stay cool, clam, and logical, not when we get angry and heated.

But the hypothetical part here isn't just the use case. It's also the outcome. And the bad outcome did not happen, the author made it up.

Repetitive focus on negative thoughts or hypothetical situations could be a symptom of anxiety or anger. Doesn’t have anything to do with tech in my experience, more with mental health in general.

Yeah, I was angry when I was writing it, not denying it.

Anger is often the only way to motivate action, since when you were calm you didn't care about solving it.

I have definitely been in dozens upon dozens upon dozens of situations where a website or app struggled to do something that my dad's PC in the 90s could do fast enough for the modem to be the only bottleneck. And even then the P1 with the modem that ran into the phone line probably still wins out, which is disgusting given that its entire disk was smaller than the RAM on my phone.

ROPs vulernabilities and lack of linux compatibility notwithstanding, i swear flash wasn't even half as bad as modern web crap.