Franck MIKULECZ's List: Quality & Standards !

• two programmers will complete that task and do so with significantly higher quality and with significantly fewer bugs
• no better way to improve the quality of a team
• combined with high-levels of automated testing, to improve the quality of the software that we create
• introduce a new member of the team and get them up to speed, or coach a junior developer and help them gain in expertise or introduce a developer to a new idea or a new area of the code-base
• the most fun
• the shared joy of discovery when you have that moment of insight that makes complexity fall away from the problem before you
• Pair programming works, and adds significant value to the organisations that practice it

5 more annotations...

• reduce the repro steps to the minimal steps to reproduce
• Anyone can resolve it
• only the person who saw the bug can really be sure that what they saw is fixed
• keep careful track of versions
• just don't accept bug reports by any other method
• don't tell them about bugs - put them in the database and let the database email them

4 more annotations...