Tag Archives: Remote

#RemotePairProgramming Ep 003: Strong Style Pairing with Michel Daviot

About

The second episode of this #RemotePairProgramming series is about Strong Style Pairing. My coding pairing partner this episode is Michel Daviot.

Strong Style Pairing

During Episode #002 Llewellyn was the Navigator in a Strong Style Pairing way. This episode I will be doing the same, but with my style. But there is also a challenge, given by my driver: Michel.

The Challenge

I don’t know at all the problem, and I have never heard of it. So I need to be navigating in a Strong Style Pairing without knowing the problem. So my solution is to go in small steps, to minimize the risk.

Remote Pairing Michel

Read More →

#RemotePairProgramming Ep 002: Strong Style Pairing

About

The second episode of this #RemotePairProgramming series is about Strong Style Pairing. My coding pairing partner this episode is Llewellyn Falco.

Strong Style Pairing

The Driver is just the typist of the Navigator

Pair-programming is a technique where two programmers stay at the same computer and code together on the same problem. We have two roles: Driver and Navigator.

Driver = the partner who writes the code, and focuses on small details, on short term.

Navigator = the partner who understands what the driver writes and focuses on long term decisions. Typically the navigator’s focus is around the design, architecture concerns, clarity, conceptual cohesion, etc.

During a session of strong style pairing, the Navigator will take all the decisions. The Driver focuses on the small details, just to do what the Navigator has in mind. If something is unclear the two have a dialogue. The same as with traditional style pairing, both roles have the same focus: try to solve the problem as fast as they can with the highest quality possible.

Strong Style Pairing

Read More →

#RemotePairProgramming Ep 001: Traditional Style Pairing

About

This is the first episode of a series of codecasts where I will explore, together with a remote (duh!) pairing partner, what remote pair-programming is. It is also about pair-programming techniques, and how they help us, or not.

My remote parter this episode is Llewellyn Falco.

Traditional Style Pairing

Two people stay on the same computer and code, for a specific problem.

But it is more than that. We have two roles: driver and navigator.

Driver = the partner who writes the code, and focuses on small details, on short term.

Navigator = the partner who understands what the driver writes and focuses on long term decisions. Typically the navigator’s focus is around the design, architecture concerns, clarity, conceptual cohesion, etc.

During a session of traditional style pairing the roles can stay the same, or they can change. But both roles have the same focus: try to solve the problem as fast as they can with the highest quality possible.

Read More →

AgileWorks Remote Open Space – First experience

AgileWorks Remote Open Space

The idea of having a Remote Open space is simple: take 30 minutes to discuss subjects of interest to you with a group of experienced people in that area of interest. You can find the description of the idea here.

I want to try doing a couple of Remote Open Space sessions to see if we will have enough attendees to start something that is interesting, useful, and easy to organize. You just need ideas, a computer with at least a microphone and 30 minutes of your time. I saw that the Romanian AgileWorks communities are not that well connected with each other. In all the communities interesting things are happening, but they do not share their experiences with each other. So the main purpose of the AgileWorks Remote Open Space is to connect online the AgileWorks communities in Bucharest, Timisoara, Cluj, Iasi, Sibiu, and Tirgu Mures.

Read More →