Discover and read the best of Twitter Threads about #pairProgramming
Most recents (4)
This week has seen us working 100% remotely and assisting our clients with business continuity. Here are some tips for #RemoteWorking during these unprecedented times...
#EasyRemoteWorking #covid19 #covid19uk #coronavirus #workingfromhome #stayathome #quarantine #staypositive
#EasyRemoteWorking #covid19 #covid19uk #coronavirus #workingfromhome #stayathome #quarantine #staypositive
1. Take regular breaks
Screen sharing & conference calls can be much more tiring than being face to face. There's more load on your brain filling in the blanks created by not seeing the people you're interacting with. Tip: try the #PomodoroTechnique
Screen sharing & conference calls can be much more tiring than being face to face. There's more load on your brain filling in the blanks created by not seeing the people you're interacting with. Tip: try the #PomodoroTechnique
2. Use Video in your conference calls
Non-verbal cues are used in face to face communication. We gesture to indicate a desire to speak, we nod, we shake our head or look confused. People adapt communication from these, so we're better placed to leave with a shared understanding.
Non-verbal cues are used in face to face communication. We gesture to indicate a desire to speak, we nod, we shake our head or look confused. People adapt communication from these, so we're better placed to leave with a shared understanding.
I can estimate how long it will take me to drive to Des Moines, and be "close enough." There are lights, stops, traffic, weather to consider, but mostly it's me choosing route and rate.
Route has speed limits, traffic features, raw distance. Those are not up to me, really. I have limits, but the limits make the trip predictable.
The fewer items are under my control, the less likely the estimation.
Can I get to des moines in 3 hours? Probably, if you provide me a fast plane or fast helicopter and clear weather. Otherwise, no.
Can I get to des moines in 3 hours? Probably, if you provide me a fast plane or fast helicopter and clear weather. Otherwise, no.
I have noticed that people who say « #pairProgramming is not for me », have generally had painful experiences that they have not yet had the opportunity to overcome.
The discomfort felt is often so personal that they wished to close this box with all that it contained.
They leave then with a certain bitterness and an idea which allows to console themselves: "it is not for me".
They leave then with a certain bitterness and an idea which allows to console themselves: "it is not for me".
Pairing is like communicating. It is sometimes extremely complicated.
This ultimately requires a lot of skill, maturity, as well as a good knowledge about oneself.
This ultimately requires a lot of skill, maturity, as well as a good knowledge about oneself.
I did a talk to a team at work yesterday about #PairProgramming. They’ve been trying it out, but they’re all new to it, so I recommend @LlewellynFalco’s Strong Style Pair Programming.
But while I was digging out some references, I came across this: scribd.com/doc/25304465. It talks about the hit that engineers get from tinkering with code until it works, then moving on.
An episode of @bosslevelpod discussed a similar idea a while ago: itunes.apple.com/gb/podcast/bos…. We like social media *because* it is often dull. We seek those rare good tweets.
