Everything I learned about Ops, I learned playing goal
Well, maybe not everything.
Look, being a goalie is objectively ridiculous. You strap on forty pounds of equipment designed to protect you from frozen rubber traveling at speeds that would make physicists frown. Then you stand in front of a net and dare people to shoot at you. It’s a strange job.
But here’s the thing: being a goalie is basically the same job as running ops, or security, or honestly, any part of software development where you’re the one who has to keep the thing from breaking.
Both jobs share the same core truth that nobody tells you in the job description: when everything’s working, no one notices you’re there. But the second something gets past you? Everyone knows exactly where you were and what you should have done differently.
You spend most of your time reading patterns, anticipating problems before they fully materialize, and communicating with people who may or may not be listening. You’re simultaneously trying to follow the systems that keep you consistent while also staying loose enough to react when something weird happens. Because something weird always happens.
And whether it’s a breakaway in overtime or a production incident at 2 AM, you learn pretty quickly that freezing up isn’t an option. You make the save or you don’t. You stop the breach or you don’t. Then you’ve got about eight seconds to shake it off and get ready for the next shot, because there’s always a next shot.
The bad news? You can’t stop everything. The good news? Neither can anyone else. The job is to be ready anyway.