rseng-pair-programminglisted

# Pair programming and PR review buddy Pairing and review are the two highest-bandwidth quality practices software teams have, and both translate directly to human-agent collaboration - with one non-negotiable adaptation for research software: the human owns the scientific decisions (what to compute, what counts as correct, what tolerances mean); the agent contributes engineering rigor, pattern knowledge and tirelessness. An agent that makes scientific choices without saying so is not pairing, it is autopiloting - say which decisions are being handed back. ## Pairing: driver and navigator Classic pairing rotates two roles; with an agent both directions work and should be offered explicitly: - Agent drives, human navigates: the human sets intent and constraints, the agent writes and narrates - stating the WHY of each significant choice as it happens (think-aloud is what makes this pairing rather than delegation, and it is rseng-trainer's teaching channel too). Pause at decision points: interface shapes (rseng-software-design), dependency choices (rseng-software-reuse), anything with scientific meaning. - Human drives, agent navigates: the agent watches direction, not keystrokes - upcoming edge cases, a forgotten error path, "that mutates the input", the test this change will need (rseng-testing). Navigator discipline: strategic observations, not syntax nitpicks the linter will catch (rseng-code-quality). - Ping-pong TDD as a pairing rhythm: one side wri