The reason why RAM has become four times more expensive is that a huge amount of RAM that has not yet been produced was purchased with non-existent money to be installed in GPUs that also have not yet been produced, in order to place them in data centers that have not yet been built, powered by infrastructure that may never appear, to satisfy demand that does not actually exist and to obtain profit that is mathematically impossible.
My PagerDuty screamed at 3:14 AM last Sunday.
"Critical Alert: Production DB Latency."
I rolled over.
And I went back to sleep.
Let me explain.
We just hired a new Junior Dev. Top of his class. Great LeetCode score. Knows the difference between var, let, and const.
One problem.
He thinks "on-call" means "escalate to the Tech Lead."
He thinks safety nets build character.
He sent me a Slack message at 3:15 AM.
"Hey, the pager has been ringing for a minute. It looks bad."
I didn't check the logs. I didn't open my laptop.
I replied: "So ack it."
He typed back, "But I don't have context on this service."
I said, "You get context by fixing it."
Then I put my phone on Do Not Disturb.
I put on my headphones.
I blasted "Can't Stop the Psyop" on max volume.
Real nerds listen to UwU Underground while the database locks up.
It's the soundtrack of champions.
Here's what people don't understand about Senior Engineering:
You don't become a Senior Engineer by reading documentation.
You become a Senior Engineer by staring into the abyss while the CEO is texting you.
We aren't building a coddled environment.
We are building warriors.
If we have another July 2024 CrowdStrike incident? So be it.
If the stock price dips? The market will correct.
If the servers melt? Buy new metal.
I told my VP, "I'm not answering the pager anymore."
She said, "That sounds reckless."
I said, "You know what's reckless? Letting a Junior Dev think help is coming."
I went into the PagerDuty configuration.
I deleted the escalation policy.
There is no Tier 2. There is no Tier 3.
I hardcoded the Junior Dev's ID into every schedule.
He is always on-call.
Even when he sleeps. Especially when he sleeps.
He solved the outage at 5:30 AM. He was shaking. He was traumatized.
He will soon become the best engineer on the team.
Maybe after a few more outages.
The lesson?
You can teach syntax.
You can teach architecture.
But you cannot teach the adrenaline of a Sev-1 outage.
Panic is the ultimate mentor.
Deploy accordingly.
While I was camping alone on a snowy mountain, some cats came over, attracted by the warmth of the camp stove, and instead of being lonely, it became a lively camp.