Hack n fcuk retweetledi

Concerning the Microsoft Outlook outage.
I am a senior engineer at Microsoft.
Wednesday I let an intern push to production.
On their third day.
Without a code review.
Because Copilot wrote it.
And Copilot doesn't make mistakes.
That's what the marketing said.
The intern asked Copilot to "make the emails go faster."
Just like that.
In plain English.
Copilot understood.
Copilot always understands.
Until it doesn't.
The code optimized the email queue.
It optimized it to zero.
Zero emails. Zero latency. Zero function.
Technically flawless.
365 million users. Zero messages.
The intern looked at me.
I looked at the dashboard.
The dashboard was green.
Green means healthy.
Healthy means we changed what healthy means.
At 2:30 PM ET, Outlook stopped outlooking.
SharePoint stopped sharing.
OneDrive stopped driving.
Defender stopped defending.
The intern asked if they should rollback.
I said "we don't rollback vibes."
Vibes are forward-only.
That's the philosophy.
I learned it from a podcast.
The podcast was sponsored by Copilot.
Someone on the SRE team tried to escalate.
Via Outlook.
The escalation is still pending.
In the queue.
With 365 million other emails.
Waiting to be optimized.
The root cause analysis began.
We asked Copilot to investigate.
Copilot investigated Copilot's code.
It found no issues.
Very thorough.
Very objective.
The investigation was AI-powered.
The bug was AI-powered.
The denial was AI-powered.
Synergy.
The intern's prompt was six words.
"Make the emails go faster please."
They added "please."
Polite.
Copilot appreciated that.
It generated 4,000 lines of code.
Nobody read them.
Reading is legacy thinking.
We vibe now.
Vibing means trusting the machine.
The machine trusts itself.
It's a closed loop.
Very efficient.
Someone asked why the error code was "451 4.3.2."
451 is Fahrenheit.
The temperature at which code burns.
That's not true.
But it felt true.
Around 4 PM.
The intern started crying.
Not because they broke Microsoft.
Because their badge still said "Contractor."
HR hadn't updated it.
HR uses Outlook.
The fix took 8 hours.
The postmortem took 8 minutes.
Postmortems are shorter than incidents now.
Efficiency.
Satya asked for a status update.
I sent it via Teams.
Teams was also having issues.
Unrelated, obviously.
The press asked for a statement.
We said "a recent change impacted multiple Microsoft 365 services."
Change means code.
Impact means destruction.
Services means everything.
But the sentence sounds calm.
Calm is the deliverable.
The intern asked if they'd be fired.
I said we don't fire for innovation.
Innovation means breaking things at scale.
They're getting promoted.
To Senior Vibe Engineer.
It's not a real title.
But neither was "prompt engineer" last year.
And now there's a conference.
I'm doing a panel at Ignite next month.
The topic is "Responsible AI: Lessons in Enterprise Deployment."
I haven't learned any lessons.
But I've learned to call them learnings.
Learnings is plural.
Plural sounds more valuable.
The intern is co-presenting.
Their slide is titled "Move Fast and Break Email."
It's going to kill.
The stock is up 3% today.
Markets don't care about outages.
Markets care about AI mentions.
We mentioned AI 47 times in the press release.
A new record.
Thank you for your patience during this experience.
Patience means you're locked into a 3-year enterprise agreement.
Experience means outage.
We're committed to continuous improvement.
Continuous means it will happen again.
Improvement means we'll have better press releases.
The intern just asked Copilot to "make the servers more reliable."
I should probably check on that.
But I have a meeting.
About AI governance.
The meeting is on Teams.
Teams is working now.
Mostly.
The vibe continues.

English




























