The Intern
Every legendary outage begins with someone brave enough to press enter without asking first.
Day One, Root Prompt
Somewhere today you get handed a login that works — a real one, not a sandbox, not a training tenant, the actual keys to something that matters. You didn't ask if you were ready and nobody checked. The cursor blinks in a terminal window you've never seen open on your own machine, and it is, against every instinct, thrilling. This is the Fool's leap in its native habitat: the moment before you know enough to be scared.
Say yes to the ticket nobody's claimed. Click into the system you've only read about in the wiki. The senior engineers you're shadowing all started exactly here, holding a runbook they hadn't finished reading, hoping the first command wouldn't be the one that mattered. Today it probably won't be. Today is for learning what the buttons do.
what may cross your path
- A new laptop, still warm from setup, lands on your desk with more access than you expected.
- Someone says 'you'll figure it out' and walks away before you can ask what 'it' is.
- You get added to a channel with a name like #prod-alerts and no explanation follows.
- A runbook you've never opened before becomes the only thing standing between you and a decision.
I don't know what this does yet. That's why I'm asking first.
The Query With No WHERE Clause
There's a beat, right after you hit enter, where the output hasn't printed yet and your stomach already knows. Something ran wider than you meant it to — a script without a dry-run flag, a command copied from a doc without reading the second half, a delete that forgot its condition. The room goes quiet in the specific way a room goes quiet when everyone just watched the same number tick down.
This is the Fool's other lesson, the one that only lands after the leap: confidence and preparation are not the same thing, and production doesn't grade on effort. Nobody who's been doing this long enough is exempt from this story — they just have an older version of it. What matters now is saying so, fast, before the silence becomes its own incident.
what may cross your path
- A command finishes faster than it should, and the fast part is the bad part.
- Someone in the channel types 'was that supposed to happen to everyone?' before you can say a word.
- You reach for an undo that this particular system has never once had.
- A senior engineer says 'we've all done it' in the exact tone that means it's worse than you think.
I broke it. I said so. That's the part that actually matters.