Revised agenda for tomorrow at 5pm BST:
- NGI while Mia’s away (5m)
- AMA prep (15m)
- Code review (40m): coding checklist
@Leonie @amelia , I realize our code reviews usually run crazy over time, so I was thinking we develop a coding checklist of 3-ish items for assessing salience of the codes. It can help us think through our codes individually as we code. And during the review, it can speed up the process and establish consistency. What do you think? Drawing from this ethnography wiki, a few starters I had in mind:
Is your code salient? Does it meaningfully capture the essence of what’s being said?
- ex) participants discussing whether something is machine learning, AI, etc. →
defining terminology
Is your code explicit? Does it make explicit what’s going on?
- ex) interviews pushing back on dominant ways of framing an issue →
nuancing the debate
andreframing priorities
Is your code congruent with other codes?
- ex) if we have already established convention for action-state codes as
being ---
then stick to the format →being practical
andbeing strategic
rather thanpragmatism
andstrategies
(former codes also more specific to what’s being captured)
What will it look like on graphryder?