HandsAtTheReady

4 ms·

1. 1.▲
   by HandsAtTheReady 8y ago

   > someone right next to you hovering while you are trying to develop The pair is a collaboration. They develop together. > Do you really need someone over your shoulder to make sure you can turn requirements into code? I listed numero
2. 2.▲
   by HandsAtTheReady 8y ago

   > The cases you see at Bloomberg are well evidence, lack of tech is not a problem here. From TFA "From about 2007 until 2012, Banamex USA, a Citi subsidiary, processed more than $8.8 billion in transactions with almost no oversight.
3. 3.▲
   by HandsAtTheReady 8y ago

   I've been at places that do those too. But they weren't the environment that has enabled my best work. In particular, PRs and design sessions were/are a context switch which add friction. Even when pairing, however, we'd
4. 4.▲
   by HandsAtTheReady 8y ago

   +1 to XP. Pairing removes many barriers to development: * built-in code review * knowledge sharing: removes silos * helps avoids overengineering (few pairs have the same overengineering idea, so you tend to settle on a decent un-overenginee