TUESDAY, 2:00 PM
Quarterly Demo Day. The most important presentation of the quarter. 150 people on Zoom. CEO, CTO, VP of Engineering, the Board of Directors, three major clients, and everyone from Engineering.
Wolfy was presenting the new Cloud Infrastructure Monitoring Dashboard. Three months of work. Real-time metrics. Beautiful visualizations. Auto-scaling insights. It was going to be legendary.
He'd prepared for a week. Rehearsed his slides. Set up OBS Studio for professional screen sharing with camera overlay. Tested his microphone. Even wore a button-up shirt (from the waist up, at least—who checks below the desk?).
Everything was perfect.
Narrator: Everything was NOT perfect.
1:55 PM - 5 Minutes to Showtime
Wolfy joined the Zoom call early. Camera on. Microphone tested. Screen share ready. His tail was safely tucked under the chair (the physical one, attached to him, not the Bluetooth one he'd learned to keep FAR away from production systems).
2:00 PM - Showtime
Wolfy unmuted himself. Deep breath. Professional smile.
He clicked "Share Screen" in OBS Studio. His carefully prepared scene switched to the dashboard demo. Perfect.
Except...
2:03 PM - The First Sign of Trouble
Wolfy's phone buzzed. A Discord notification from FurryTech Community Server. He ignored it. Professional mode activated.
But then another notification. And another. His phone was on his desk, screen visible to his webcam. The notifications kept popping up:
Wolfy's blood ran cold. His ears—the furry ones on his headband that he wore during "personal streaming sessions"—were still on his head. He'd forgotten to take them off.
But wait. That wasn't the worst part.
The Discord notifications said "YOUR STREAM IS LIVE."
He wasn't streaming to Discord. He was presenting to 150 coworkers on Zoom.
...unless...
2:04 PM - The Horrifying Discovery
With mounting horror, Wolfy alt-tabbed to OBS Studio. And there it was:
Streaming to: Twitch (FurryWolfy247) 🔴 LIVE
Viewers: 847
Duration: 4:23
OH NO. OH NO NO NO NO NO.
He'd been streaming his CORPORATE DEMO to his FURRY TWITCH CHANNEL for the last 4 minutes.
But HOW? He'd set up a scene called "Work Presentation" that was supposed to be for Zoom only. Except he'd apparently left his Twitch stream settings on from last night's "Coding with Wolfy: Building a Tail API" stream.
2:05 PM - Panic Mode
Wolfy was still talking. On autopilot. Showing graphs. Explaining metrics. While simultaneously having a complete internal meltdown.
His Twitch chat was EXPLODING:
And then, the worst possible thing happened.
Someone from his WORK noticed his Twitch stream.
ABORT ABORT ABORT
2:07 PM - The Decision
Wolfy had three options:
He chose Option 1.
Mid-sentence, while explaining auto-scaling policies, Wolfy clicked "Stop Streaming" in OBS.
And OBS, being OBS, crashed completely.
His Zoom screen share froze. His camera went black. His microphone cut out.
On 150 people's screens: CONNECTION LOST
2:08 PM - Chaos
Wolfy frantically restarted OBS, switched to native Zoom screen share (no OBS overlay), ripped off his furry ears, and rejoined the call.
2:10 PM - Recovery Attempt
He shared his screen. Dashboard was still there. Perfect. He resumed the presentation.
But then Sarah (CTO) spoke up:
Silence. 150 people waiting for an answer.
Wolfy's brain went into overdrive. What could he say?
SMOOTH SAVE.
2:25 PM - The Aftermath
The rest of the presentation went perfectly. No more crashes. No more Twitch streams. No more furry ears. Just pure, professional DevOps content.
The dashboard demo was a hit. The CEO called it "transformative." The CTO said it was "exactly what we needed." The clients were impressed.
But later that day, in the team Slack:
PLOT TWIST: Jake was also a furry.
LATER THAT NIGHT
Wolfy posted on his Twitch:
The stream got 1.2K viewers that night. His Twitch followers grew to 2,100.
And the next day, three different coworkers quietly followed his Twitch channel.
Turns out, the tech industry has more furries than you'd think. 🐺