- Define the incident owner
- Define the incident secretary/communicator
- Create and document
- Summary
- Observations (link to metrics dashboards with absolute timestamps as much as possible)
- Screenshots
- Who took the screenshot
- Link to get the graph/data
- Associated conclusions
- Links to logs
- Screenshots
- Hypotheses/theories
- Who made them
- When
- If they have been validated/invalidated
- The actions taken
- By whom
- If it had the desired effect
- etc.
- In the situation where an incident has been caused by the introduction of a code regression, revert the change and deploy as soon as possible
- Start by reducing/relieving the impact of the incident before searching for a root cause
- Use multiple data sources when data sources do not agree
- Diagram all the implicated systems and the relationship to one another in order to identify the potential locations where the problem might be
- Test your hypotheses to verify if they hold or not
- Develop a procedure over time that can be followed to diagnose similar issues
-
Write down a list of improvement suggestions in order for the incident not to reproduce itself in the future or to lessen its impact
- Once the incident is completed, have a summary of the conclusions at the top of the document with a link to the sections in the document explaining the rationale behind the conclusions
- Identify the cause of the problem
- 5 whys
- List potential solutions
- Investigate potential sources of similar problems
- Address the additional sources of risk
- Reduce incident duration
- Identify the cause of the problem more rapidly
- Reduce incident cost
- Reduce the number of people involved
Every year, either at the beginning or end of the year.
A few hours spread over the course of a few days.
- Review year according to various facets
- Plan the next year according to the same facets
- I use a mind map software to do my yearly review and plan.
Every month, either at the beginning or end of the month.
30 minutes.
- Review what was planned for the month
- Provide feedback related to the plan
- Review yearly plan and align
- Plan next month
- I use a text editor, such as VS Code, to write my monthly reviews.
In this article I define a 1-5 rating scale for books in order to be consistent across my evaluations. Given that rating books is somewhat subjective, introducing some amount of standardization on how I rate them should help with managing my reading.
Format of presentation:
Score (from 1 to 5) Representative emoji
- Satisfaction
- Words expressing the level of satisfaction
- Strength of recommendation
1 đ¤Ž
- unsatisfactory
- very bad, horrible, boring, repetitive, disagreeable to read, waste of time, can't force myself to read
- strongly not recommended
2 âšī¸
- unsatisfactory
- bad
- not recommended
3 đ
- satisfactory
- neutral
- might want to read
4 âēī¸
- satisfactory
- good
- recommended
5 đ
- satisfactory
- very good, great, amazing, exciting, intriguing, fascinating, full of new knowledge, can't stop reading
- strongly recommended