Making Code Review Meetings more Streamlined
at our meeting today @katejsim and I discussed ways to make out bi-weekly meetings more structured so that we are all on the same page and don’t have to go over time as much.
(1) flag codes ahead of time that we are unsure about or want to discuss during the meeting. Post these here before meetings.
(2) review codes by thematic area rather than by order of occurrence
(3) if you are working on certain thematic/conceptual areas, flag/describe them here before meetings if it will help contextualise your codes.
(4) review codes using the three categories we established:
(a) salience: does the code meaningfully capture the essence of what is being said?
- ex: participants are discussing whether something is, e.g., machine learning:
defining terminology
(b) explicitness: does the code make explicit what is going on?
- ex: interviews pushing back on dominant ways of framing an issue:
nuancing the debateandreframing priorities
(c ) dynamism: does the code follow established convention and is it clear enough to work in different threads?
*ex: if we already have an established convention for action-state codes, e.g. being practical, being strategic, stick to that format. These kinds of codes are broad enough so that they will be usable across different threads, but concrete enough so that they aren’t vague (as opposed to pragmatic or strategic).