News for hackers. Stuff that matters.
Re:Things I Learnt from a Senior Software Engineer by bryanrasmussen on Monday August 26, 2019 @12:49AM (#20797520)
pair programming is really a forced socializing in a field where a lot of people have trouble socializing, never really understood how it got as far as it did.
Re:Things I Learnt from a Senior Software Engineer by TeMPOraL on Monday August 26, 2019 @06:47AM (#20798720)
Pair programming is an anti-procrastination trick that works by setting two people in a situation where both are afraid to lose face by trying to goof off. This works, but builds up anxiety.
Re:Things I Learnt from a Senior Software Engineer by neilv on Monday August 26, 2019 @03:08AM (#20797986)
Pair programming seems to be social in some ways, but I could imagine two programmers with very little social awareness or self-consciousness being able to find a cadence for pair-programming.
Re:Things I Learnt from a Senior Software Engineer by filoleg on Tuesday August 27, 2019 @03:03PM (#20813301)
Depends on the definition of pair programming imo.

Bad definition (the one I encountered in school): two people of about the same skill level sitting at one computer and programming together. I hated it, akin to my hate of backseat drivers.

Good definition (the one I encountered at my workplace): as a junior engineer, I was tasked with implementing this tricky caching thing in one of our systems that I had zero previous experience with. One of our senior engineers was tasked with helping me with that. I would implement as much as I could myself, and when I get stuck, the senior would either give me hints on how to get unstuck or program some parts himself while explaining to me how and why he did things a certain way. This helped me out tremendously in my skill development and got me running confidently in our codebase really quickly.

Re:Things I Learnt from a Senior Software Engineer by larzang on Monday August 26, 2019 @08:29AM (#20799262)
Interaction between devs is unavoidable, at the code review stage if not sooner. Pair programming provides tighter feedback loops and helps get things done quicker than playing CR tennis after a lot of hours have been sunk into something.