pair-programming-tips.txt

Tests
- what tests do we want to write?
- write up a test plan
- did we write a testable solution
- do we want to test this on staging?

Design
- Did we follow coding standards
- Did we follow product/design standards
- How could this fail? How do we want to handle these failures?
- Do we intrododuce obvious performance/scalability bottlenecks
- Are we securely handling untrusted content (e.g. sanitization)?
- Step back and ask, "is this a well-designed solution?"
- Have we solved a similar problem we can build off of?
- Are we solving the right problem?
- Is these a simpler solution?

Time
- Is this taking longer than we planned?
- Are we in a rabbit hole?
- Is now the right time to shave this yak?

Tangential Tasks
- Are we focused or have we gone off in a tangent/distraction
- If you notice a bug, make a note to file a ticket
- If you notice chores (refator, delete, document, etc) make a note to file a ticket
- When testing the product, note ideas for fixing or improving the user experience
- Note lesons to share with the team. For example, if you discover an
  anti-pattern in our code, make a note to teach the team - via email or retro -
  about it
- Seek out places where an internal tool would save us a lot of time. If you
  discover one, make a note to build it.
- How could we have finished this task faster? What slowed us down the most?
  What was the most frustrating?
- How could we have done that better? What if we spend more time reviewing the
  technical design upfront?
 
Feedback for the driver
- Carefully observe the drive and write down suggestions on ways they can improve.
  Think about how a gold coach watches a player drive the ball, over and over
  again, and then givers pointers on how to improve