addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [ljc] Am I a bad programmer if I do not like pair programming?

From: Colin V.
Sent on: Wednesday, January 30, 2013 10:12 AM
Hi Matt,
 
Concerning pair programming and TDD. I personally think TDD (and design by contract) philosophy, can contribute to overly constrained code. I could argue that Pair programming helps mitigate this, because the pairing partner might point out more general applications for interfaces, and avoid a tendency to beat the potential for reuse out of the code...

Could you expand more on why you think TDD contributes to overly constrained code?
 
Concerning code reviews, I have found they are unpopular among some developers, and can get 'forgotten' fairly quickly, as a thing you can get away with not doing. Pair programming can give similar benefits as code review, at the point of coding, rather than retroactively.

I've never managed to work anywhere where code reviews actually happen on a regular basis.  They come and go, and are always the first thing to be thrown out when time gets a little bit tight.  I've often found the other problem with code reviews is that regardless of how they are run, there is always someone in the room who will feel like their work is being singled out.
 
- we don't go to work just for fun. If you don't like pair programming, be creative and invent alternatives. We will thank you for inspiring us with new approaches...


+1 for this, and not just on pair programming.

I would add that if you're really not a fan of pairing (it's not for everyone) and wouldn't like being "forced" to do it all day, every day, this is something that should be brought up during an interview for a position, as should anything you're not happy with.  The worst thing to do would be to take a position at a company who is dedicated to pairing and expect them to change for *you*.

Our Sponsors

  • Our Blog

    Read the latest news from the LJC

  • RecWorks Ltd

    Fixing Tech Recruitment using the Power of Community

  • jClarity

    Java/JVM Performance Analysis Tools & mentoring for Java related matters

  • LJC Aggrity

    Our LJC Aggrity site contains blog posts from our members

  • LJC Book Club

    Our Book club with book reviews from our members

  • Devoxx UK

    Java Community Conference in collaboration with the LJC, 8-10th June 16

  • SkillsMatter

    "Host, help organise, promote, film many of our meetings."

  • IBM

    Build Enterprise-grade apps at start-up speed.

  • New Relic

    New Relic makes sense of billions of metrics a day in real time.

  • Hazelcast

    Hazelcast is the leader in operating in-memory computing.

  • Java.Net

    We are an official Java User Group recognised by Oracle's JUG program

  • JRebel

    Free 3 month J-Rebel license.

  • O'Reilly

    40% discount on printed books and 50% on e-books.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy