In this week’s podcast Wes Reisz talks to Neha Batra, a software engineer at Pivotal Labs. Neha spoke about pair programming in her recent QCon San Francisco 2016 presentation, and has taken time to discuss techniques to get started with the practice as well as tips for implementing it on your team. Neha also touches on vulnerability based trust and how it can help effectively build a trusting team environment.

Why listen to this podcast:

- If you successfully start with pair programming, other tenants of XP are pulled along with you

- Ways to get creative with remote pairing to make it work

- The daily retro

- Overcoming hesitance with managers when trying to implement pair programming full time

- Vulnerability based trust building

Notes and links can be found on: http://bit.ly/2i2a0sJ

How has Pair Programming Evolved Over the Years?

6m:17s - A lot of the fundamentals are the same, but with XP we take it to the extreme to be able to do it eight hours a day.

6m:24s - To pair for eight hours a day we adapt to a lot of other process to create a simpler way of working, giving us an easier level to default to.

6m:44s - We use phrases in the team to make sure we agree on a test, that there are no false positives, when to refactor etc. This helps us avoid accruing code debt since we don’t do code reviews.

More on this:

Quick scan our curated show notes on InfoQ. http://bit.ly/2i2a0sJ

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq