Tinker Observability & error analysis

by Kondasamy Jayaraman · drawn with Colorfigures by April Zhu

Groups, front left to rightGroup 1: 0 · Group 2: 0 · Group 3: 0 · Group 4: 0 · Group 5: 0

Chapter 4 of 7

Axial coding

You have a note for every failed trace. Read together, some notes say the same thing in different words.

This chapter: How do notes become a short list of failure modes you can count?

You will learn

  • Axial coding: grouping notes that share a cause
  • Failure modes: the groups, named by what went wrong
  • Counting how often each mode happened
Words you’ll meet (2)
Axial coding
Sorting open notes into groups that share a cause, then naming and counting the groups.
Failure mode
One kind of failure, such as “answered from an old passage”, with the traces that show it.

The picture on the left is live. Each step below asks you to do one thing in it; the story continues here as you go.

Step 1 of 3

Every failed trace has a note now: yours where you wrote one, the suggested one where you didn’t. Axial coding sorts the notes into groups that share a cause. Each group is a failure mode. Before you sort:

Once the notes are grouped, which kind of failure do you expect to be the most common?