Use a code freeze as a reminder that there are still quirks to be worked out, and make an effort to work them out.

What lessons can you take from this incident for your own organization?

Facebook has revealed the cause of their 6-hour outage: human error. I hope those pesky humans learned their lesson! Or is there more to it?

If your team is open to it, by all means, start doing retrospectives. But if you sense resistance, here are some reasons to start with postmortems.

DevOps is a big topic, and simply knowning where to start can be a mystery. I have two suggestions for how you can start with DevOps today.

Next time you have an unexpected outage, take note, document it, and consider coming up with a mitigation strategy.

In this episode of Tiny DevOps, guest John Goerzen applies his experience as an amateur pilot to IT risk management.

Something has gone terribly wrong. You and all the king’s men have risen to the occasion, and put Humpty Dumpty together again. What next? You’ve heard of postmortems, and you think doing one could help you, but where to begin? This guide is for you! With literally no preparation, you should be able to run a successful postmortem. Even if you found this via google after assembling in the conference room!