Postmortems
A postmortem (or post-mortem) is a process intended to help you learn from past incidents. It typically involves an analysis or discussion soon after an event has taken place.
“Whatever you do, you will make mistakes, errors and blunders. Everyone does. Some less, some more, but no one is exempt. Yet, success is nothing more than mistakes you managed to overcome. That is why a mistake is not important. What counts are the things you do after one.”
TIP: If you want to know more about the concept of postmortems and its purpose and usage, please refer to a blog post I wrote some time ago. I’m pretty sure that will help even more.
Modular Monolith: DB Schema Migration failure led to an outage.
LESSON LEARNED: Plan upfront any DB Schema Migration that includes Data Manipulation. Continue reading Modular Monolith: DB Schema Migration failure led to an outage.
Kubernetes Node tainted, blocked Pods triggering a 503 (Service Unavailable).
LESSON LEARNED: Setup proper alerting and use the best monitoring practices in order to act rapidly in case of an issue/outage/problem. Continue reading Kubernetes Node tainted, blocked Pods triggering a 503 (Service Unavailable).
iOS CI Broken due to Personal Accounts used to build the client.
LESSON LEARNED: Personal private accounts should never be used in order to avoid coupling outside the Organization we are working for. Continue reading iOS CI Broken due to Personal Accounts used to build the client.
Android Inconsistent DB Schema when migrating from SQLite to Room.
LESSON LEARNED: Every team should establish a communication channel with other teams to favor collaboration and contribution. Continue reading Android Inconsistent DB Schema when migrating from SQLite to Room.
