Lone Wolf vs Pair Programming: how about both?

Javalobby is asking one simple thing: are you into pair programming or prefer to perform all the work alone. The article does a pretty good job in showing the advantages and disadvantages of either of them, but then just tries to ask you whether you’re in one side of the barricade or the other, with most of the comments being nothing more than the resulting flame war. I doubt making a holy war of such an issue is the right way to go, the same I doubt there’s an universal solution to all problems, in this case The Right Way to code.
Maybe the solution lies somewhere in the middle, personally I like pair programming for critical sections or some important core modules, it makes me feel safe having two people looking and thinking the same thing. Pair programming doesn’t mean two people looking to one screen, nowadays with laptops becoming more vulgar you can have one person writing code and other reviewing it but also searching for online help or updating documentation. On the other hand, for boilerplate code, which probably includes the vast majority of the code base in normal projects, it’s much faster not having someone on your side.

Lone Wolf vs Pair Programming [Java Lobby]

Related Posts (generated)

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Switch to our mobile site