Pairing should be a given. Even before you take into account the time spent fixing defects produced by lone wolfs, very few programmers (who don’t have too big an ego to do it) will fail to be twice as productive with a pair. Once you add the knowledge sharing and mix in a bit of time you are starting to get massive gains. Why? Because although we are smart, a single programmer can’t see both the wood and the trees.
Come say hello at...
No upcoming events
- RT @cheltenhamgeeks: We’re back on thanks to some help from @CBrownRiver and @rippo: Headless UI testing with Chrome and Puppeteer https://… 6 days ago
- New Blog Post: “How Agile thinking can liberate the workplace” firstname.lastname@example.org/h… 1 week ago
- RT @RiverAgency: Wow, what a year! Today's our last day in the office before a well deserved rest with friends & family. Happy Christmas to… 3 weeks ago
- @CBrownRiver Yikes. Watched @WeAreTheCircle last night and kept wondering if it was an insite into the future of @RiverAgency ;-) 1 month ago
- RT @adampknight: Posted yesterday on using the 'Myths of Creativity' to establish a principled approach to Innovation in my organisation ht… 2 months ago