profile

Geshan Blog

Geshan's Blog Newsletter Vol2 Issue 4 - blameless postmortem + shameless processes = ...

Published about 2 years ago • 1 min read

Hello!

It is that time of the month for the Geshan's blog newsletter.

In this issue (the 5th one) we will learn about blameless postmortem and shameless processes. And the usual round of links, let's get going.


Blameless postmortem + shameless processes = better engineering

Most of us have deployed a change and unknowingly brought down production. Sometimes it is not even a deployment may be one simple API call and due to a wrong config the website came crashing down. Any P1 (priority 1) outage surely calls for an incident postmortem. It is a usual process followed by many companies which needs to be blameless.

Blameless postmortem needs shameless processes to follow it

Blameless postmortems

Any major incident that causes big outage demands a postmortem. They are a written record of the cause, timeline and the mitigation process. Of course, this process is blameless rather than pointing a finger to a person the main point is to get the broken system(s) working first and then try to figure out how the process can be improved. Humans can make mistakes the systems should be set in a way that the mistakes can be minimized or even eliminated if possible.

Shameless processes

Postmortems are done, may be a fix is also in place to keep the incident unique. The follow up part to not blame any person later is important. The process that follows on should be shameless not shaming any person that they brought down the system/website some weeks/months back. This is something the whole engineering team needs to practice and be careful about.

Finally, surely keep the postmortems blameless but keep other processes shameless too, like not digging old wounds and scars to have a better engineering culture on the whole. Kudos, keep on reading.


Blast from the past

Geshan's blog has been online for 15 years now. This is a post from 2014 about 4 git tips beyond the basics is still very useful. I have been using git even before GitHub :)

4 git tips beyond the basics - diff, global git ignore, stash, squash

I hope you like it!


5 links of the month


Here are some links that you would like:

Thats it for this edition, see you in the next one. Keep visiting Geshan.com.np.

Geshan Blog

Read more from Geshan Blog

This time it is an update about the latest blog post: 10 useful Docker commands to get things done with a real-life example Docker packages software applications into containers making them easy to build, test, and ship (deploy). In this post we will look into some useful docker commands you should know about with real-life example of MySQL docker image from DockerHub and running container. The table of contents of the post is below: Table of contents Prerequisites Example Docker Commands...

almost 2 years ago • 1 min read

Hello! It is that time of the month for the Geshan's blog newsletter. In this issue (the 4th one) we will learn quickly about when to build the right thing and when to build the thing right. And the usual round of links, let's get going. Build the right thing and build it right too This is a burning question as always how to build the right thing (software) and how to build the thing right (proper process and quality). Mostly both things would be needed but making optimal tradeoffs are...

about 2 years ago • 1 min read

Hello! Thank you for subscribing to my newsletter, Happy new year 2022. I hope this email will be better than the past 2. This is the third issue which will have a post about how to have a side income with writing as a software engineer and the regular links of the month towards the end. Won't it be great to earn some extra $$ this year? Let's get rolling! How to generate a side income by writing as a software engineer Writing is one of the most important skills we will need as software...

over 2 years ago • 3 min read
Share this post