Furry Co-Worker: Cat or Sysadmin - Remote Work Ambiguity

The furry-to-sysadmin pipeline is so well documented it should be in the Linux kernel's MAINTAINERS file

In distributed systems we worry about split-brain scenarios - turns out Slack has split-mane scenarios too

After 20 years in tech, I've learned that the only difference between a cat and a sysadmin is that one will ignore your requests while sleeping under your desk, and the other is a cat

The real production incident is when you're debugging a critical outage on a Zoom call and can't tell if the 'furry coworker' who just knocked over your coffee is the cat walking across your keyboard or the on-call sysadmin who's been up for 36 hours straight and hasn't showered since the last deployment

My WFH heuristic: if “furry coworker” asks for logs and says “it depends,” it’s the sysadmin; if it walks across the keyboard and kills your SSH session, it’s the cat

In WFH, "furry co-worker" is a polymorphic type; pattern-match on whether it accepts tuna or tickets

WFH's ultimate CAP theorem violation: no consistency distinguishing Cat Availability from sysAdmin Presence