The neverending griefing discussion
I've been doing MMOs and online worlds a long time. And that means that I've written and said a lot of things on the Internet over the years, about designing them.
One of the funny things about reactions to the various vision blogs for Stars Reach is the number of people who have
https://www.raphkoster.com/2024/08/07/the-neverending-griefing-discussion/
#GameTalk #Gamemaking #GameDesign #griefing #postmortems #StarsReach #starsreach #VwDesign
Later this month, we'll have the recording of our second episode of #OfficeOfTheITGuy. I am seeking a seasoned guest to talk about incidents and #postMortems. Extra credit if you have something to showcase on the show. #IT #DevOps #Podcast
@thisismissem @sgf "blame" is not the same thing as "assigning responsibility".
A good red flag for this is teams that say "We do #blameless #postmortems by not naming anyone in the postmortem".
No! You know you have a blameless postmortem culture when you *can* name people in postmortems without it causing problems.
This can be exceptionally hard to achieve, but it's worth it.
Edit: see also @danslimmon https://blog.danslimmon.com/2023/04/20/its-fine-to-use-names-in-post-mortems/
heard that Twitter is DDoSing itself (?)
This is a good opportunity to announce I specialize in software perf & scalability. Reducing hosting costs. And parachuting in to solve hard bugs or otherwise "rescue" sites or projects farked up by a prior approach
as a paid consultant
#DDoS
#Twitter
#performance
#scalability
#scaling
#tuning
#CostReduction
#ResourceMinimization
#troubleshooting
#rescues
#rewrites
#systems
#RootCauseAnalysis
#regressions
#postmortems
#architecture
#efficiency
#SRE
It's fine to use names in post-mortems (~300w)
https://blog.danslimmon.com/2023/04/20/its-fine-to-use-names-in-post-mortems/ #devops #sre #postmortem #postmortems #incidentresponse
"Eventually this customer has had enough. They leave. This represents both a sizable blow to revenue and a scathing indictment of your product’s reliability at scale. But, on the bright side, both MTTR and MTBF benefit enormously! That’ll look great on the quarterly slide deck." (~700w)
https://blog.danslimmon.com/2023/04/04/incident-metrics-tell-you-nothing-about-reliability/ #sre #devops #incidentresponse #postmortems
We do that anyway after incidents with #postmortems, but good time to reflect on procedures that we typically do.
Can absolutely recommend this practice, it also is a great time for the team to share past #incident stories with each other...
[4/6]
There's still value in low-technical postmortems.
What made this incident low impact? has your team implemented various safety nets to reduce harmful effects?
How did you know that a rollback was the right thing to do?
Could you have implemented a fix-forward instead?
Who else did you need to involve? or were you able to fully execute the incident and any runbooks by yourself without disrupting anyone else?
#Incidents #IncidentResponse #IncidentManagement #Postmortems #ICM #IRM
@nova @hazelweakly As a seasoned developer/etc who's also had to do devops work, I deeply appreciate your postmortems. I love the transparency with the community.
And SO well done! And I'm actually going to borrow some of the sections for our company's. 💯 ❤️
pleased with this slide of mine from our monthly major incident meta-review, encouraging us towards #LearningFromIncidents and away from focusing on incident statistics
the first half says: "The insights generated from reviewing incidents are primarily qualitative, because incidents are emergent behavior"
the second half says "There is no relationship between the impact of an incident and the quality of insights generated through the review process"
Just #ELI5'ed #postmortems to my 6yo.
2011, Los Alamos, at a for-profit nuclear lab:
"Technicians settled on what seemed like a surefire way to win praise from their bosses: In a hi-tech testing and manufacturing building pivotal to sustaining America's nuclear arsenal, they gathered eight rods painstakingly crafted out of plutonium, and positioned them side-by-side on a table to photograph how nice they looked."
#postmortems of failures in our technology, a whole forum to enjoy, recently updated with today's Cloudflare outage and a collection of other BGP mishaps:
(boosts welcome!)
The joys of #DistributedSystems and #CacheCoherency:
"A Decade Of Major Cache Incidents At Twitter", Dan Luu (https://danluu.com/cache-incidents/).
On HN: https://news.ycombinator.com/item?id=30295542
On Lobsters: https://lobste.rs/s/nrjxn2/decade_major_cache_incidents_at_twitter
#FaultTolerance #Reliability #Postmortems #Incident #Downtime
Today we experienced an issue with outbound mail for roughly an hour. The details are too extensive to go into here, but have been posted in our #postmortems channel at chat.mxroute.com.
Jonathan Hall of the Tiny DevOps Guy podcast interviewed me for episode 2! https://www.youtube.com/watch?v=-i-zRZ8nRao I discussed how #aviation can give us lessons for tech. Some of the topics included #postmortems, human factors impacting performance, accident chains (in both aviation and IT), safe attitudes, etc.
Postmortem for Banshee outage this morning available in #postmortems channel at chat.mxroute.com (uses portal.mxroute.com login).
Arrow, Lucy, Safari, and Friday are back online. Postmortem in the #postmortems channel at chat.mxroute.com.
"US nearly detonated atomic bomb over North Carolina – secret document"
Do you like #postmortems ?
Sign up at the #postmortem forum!
https://postmortems.info/
https://www.theguardian.com/world/2013/sep/20/usaf-atomic-bomb-north-carolina-1961
