> Qualitative Analysis
Path B — Reviewing & Defining Themes
Generating, reviewing, and naming reflexive themes. · 10 min
Codes are not themes. A theme captures a patterned meaning organized around a central idea (Braun & Clarke, 2022). Building them is the affinity move: cluster related codes, then ask “what’s the story these tell together?”
- Generate candidate themes. Cluster codes that share meaning (an affinity-diagram move).
- Review against the data. Does each theme hold across the extracts? Split, merge, or drop.
- Define and name. Write a sentence or two stating each theme’s central organizing concept.
- Select compelling extracts that evidence the theme, and weave them into the write-up.
Path B’s themes
Reflexive themes read the debugging experience interpretively — about identity, isolation, and access:
Asking for help as social risk
Help-seeking is experienced not as a neutral act but as a move that risks one’s standing as a competent student — so it is delayed, hedged, or avoided.
Debugging as lonely trial-and-error
In the absence of shared method, debugging becomes a private, improvised, often isolating struggle.
The error message as gatekeeper
Tool output is read as withholding access — talking past the novice rather than guiding them in.
With both paths’ themes now in hand, the next lesson — Comparing the Two Paths — sets them side by side: the same interviews, read two ways.