@CrazyVibes_1 I met a man on the train one afternoon who noticed I was reading, asked me about the book and explained he spent every day reading in our state library. He was homeless and jobless but spent his days reading, then played pool to win enough money to get by. Books change lives.
Update from Microsoft.
Teams is down.
Messages are delayed.
Some aren't arriving at all.
We're investigating.
Investigating means the AI is investigating.
The AI that wrote the code.
That broke the code.
That is now debugging the code.
It's a closed loop.
Very efficient.
A user asked why their message didn't send.
I said "we're observing recovery in our telemetry."
They asked what that means.
I don't know what that means.
But the dashboard is green now.
Green means fixed.
Fixed means we changed the threshold for green.
The messages are still delayed.
But the dashboard doesn't know that.
Dashboards don't use Teams.
Someone on the infrastructure team tried to escalate.
Via Teams.
The escalation is still pending.
Somewhere in the queue.
With everyone else's messages.
The irony wasn't lost on them.
But the message was.
We have a backup communication channel.
It's email.
Email is also having issues.
Unrelated, obviously.
The root cause is under analysis.
Analysis means we asked the AI.
The AI said "no issues detected."
The AI wrote the detection system.
It detects what it wants to detect.
Very self-aware.
Not in the good way.
Last quarter I said 30% of our code is AI-written.
Teams is closer to 45%.
We were proud of that.
Past tense.
The AI optimized the message queue.
It optimized it to zero.
Zero messages. Zero latency.
Technically correct.
The best kind of correct.
Enterprise customers are asking for an RCA.
RCA means Root Cause Analysis.
The root cause is velocity.
We shipped faster than we understood.
Understanding isn't in the OKRs.
Shipping is.
We shipped.
Someone asked when Teams will be fixed.
I said "we're continuing our analysis."
Continuing means we started.
Analysis means looking.
Looking means hoping it fixes itself.
It usually does.
If you refresh enough.
Refresh is the user's responsibility.
We provide the experience.
They provide the resilience.
That's partnership.
The outage started at 2:30 PM ET.
Right before the holidays.
Millions of workers couldn't message their teams.
Some called it a disaster.
I called it "an unplanned wellness moment."
Productivity is a spectrum.
We're exploring the lower end.
The AI has proposed a fix.
The fix requires a deployment.
The deployment system uses Teams for notifications.
The notifications are delayed.
We're in a loop.
The loop is also AI-designed.
Very elegant.
From a certain angle.
Satya asked for a status update.
I sent it via Teams.
He hasn't responded.
I assume he's thinking about it.
The stock is up 2% today.
Outages don't move markets.
Narratives do.
The narrative is "AI efficiency."
The reality is "Teams is down."
But reality isn't in the earnings call.
The narrative is.
We're committed to reliability.
Reliability means it worked yesterday.
Yesterday is our SLA.
Thank you for your patience.
Patience means you have no choice.
We're in your enterprise agreement.
For three more years.
The circle of innovation continues.
📷 Self-portrait time! This scene features black negative space and rainbow colors. Can you guess where I am? (hint: I posted photos from here yesterday, a place with a lot of tubes!) #SelfPortrait#Photography#AbandonedPlaces#Urbex
I was in the middle of shooting my narrowband data on this galaxy when the supernova happened so I was probably one of the first people to photograph it!
@SCentralized I always thought he was wrestling with mixed emotions. Yes, the tide was turning, but they’d just killed thousands of people on that super star destroyer. I liked the idea that even when battling the Empire he felt the weight of his actions.