> Qualitative Analysis
Comparing the Two Paths
The same interviews analyzed both ways — codebook and reflexive — theme by theme. · 6 min
You’ve now walked both paths on the same interviews — coding them and reaching themes via a shared codebook one way, and coding reflexively and constructing themes the other. Here is the payoff, side by side.
Same data, two valid readings
The two paths reach a matched theme for each phenomenon — built from the same interviews — but frame it differently. Read each row across: descriptive and reliably codable on the left, interpretive and researcher-constructed on the right.
Help-Seeking Anxiety
Students delay or avoid seeking help because asking feels like exposing incompetence. Seen in P3 (the linked-list wait) and P7 (not wanting to bug the TA again).
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.
↔ The shift Path A names the feeling (anxiety about asking); Path B reads what’s at stake — asking risks your standing as a competent student.
Improvised Debugging
Without systematic methods, students fall back on self-taught trial-and-error tactics. Evidenced across P3, P7, and P9.
Debugging as lonely trial-and-error
In the absence of shared method, debugging becomes a private, improvised, often isolating struggle.
↔ The shift Path A catalogs the tactics (improvised, unsystematic); Path B reads the experience — a private, isolating struggle.
Error Messages as Barriers
Opaque tool output stalls progress and can end a work session. Seen in P7 (type-mismatch error) and P9 (segfault, stack trace).
The error message as gatekeeper
Tool output is read as withholding access — talking past the novice rather than guiding them in.
↔ The shift Path A treats output as an obstacle that stalls you; Path B reads it as a gatekeeper that withholds access and talks past you.