4 ms·
Pair programming for sure. Senior designs the code, junior writes it. Senior doesn't touch keyboard. It's real time code reviewing. The senior's time is rarely
by muzani 9y ago
Pair programming for sure. Senior designs the code, junior writes it. Senior doesn't touch keyboard. It's real time code reviewing.
The senior's time is rarely wasted. They can always do time consuming high level work like designing test cases, planning out the next part of the work, seeing if the API supports stuff.
- nunez 9y agoYour company has to have the right culture for this. Companies like this are rare. Most just assign whatever's in the queue to whomever's going to take it, meaning that everyone has "something" to do at all times.
- meuk 9y agoUgh, yeah, this is horrible. Especially if you're at a company which doesn't have any documentation, and the rest of the team is in another country with 3 hours of time difference, so you're on your own after 3PM.
- crdoconnor 9y agoCompanies that permit pairing are not rare.
- nunez 9y agoThey are in my experience with several large corps.
- a-priori 9y agoI think the critical aspect here is the management system. Pair programming makes total sense when tasks are owned by the team. In that case it's in everyone's interest to improve the team's overall velocity. That means time spent mentoring juniors or working together on tasks is well spent. When tasks are owned by individuals, it's in everyone's interest to increase their own velocity which means maximizing time spent working on their own tasks. People are disincentivized from helping other people complete their work or mentoring them, because that directly reduces your personal velocity.
- ctvo 9y agoPair programming works for specific people, for others it's an exercise in anxiety. Especially in the scenario you're suggesting with a senior watching a junior write code.
- proverbialbunny 9y agoYep. Pairing a senior with a junior has showed that it does not often help juniors beyond the rate they'd normally grow at on their own. It appears like pair programming is accelerating learning when in reality it can actually hinder progress. However, pair programming has shown to accelerate growth when both peers are roughly at the same level. For some companies this means hiring two juniors and having them work together, but this isn't as common of a practice as it could be. One solution I've found to this is to subtly pretend to be forgetful and or anxious when pair programming with a junior. This lowers my level down to their level giving them growth potential. If the junior is anxious, showing anxiety about myself in a subtle way will lighten their anxiety. This works during interviews too. Being non-judgemental and friendly work too to melt anxiety away. If I am randomly forgetful from time to time, it gives them an opportunity to shine and help out leaving them feeling good and accelerating growth. Studies show that optimal learning has roughly 75% failure and 25% success. Is your jr helping you 20-25% of the time? How I encourage this growth is I start with forgetting a bit of language syntax, then a language idiom or two, then library syntax, then parts of the framework, and so on. The key here is to not show any sort of judgement. It's 100% okay if they do not know. That's part of the point. They have to look it up and figure it out and help out and grow. By doing this their level increases. My back story usually is, "Oh Python? I don't know that language. We'll have to run through it together." works like a charm as long as I start low and find their level, instead of overwhelming them. When pair programming with a junior I find 30 minutes to 2 hours at a time works best. It's slow going at first, but by giving them something to grow on, the second you leave them to their own devices they will continue to grow in that area. You can leave them alone sometimes for a week at a time and watch the results from a 30 minute pair programming session.
- muzani 9y agoYeah I think it's the vulnerability that's important too. Anxiety applies to the senior as well as the junior. Senior programmers feel they need to look competent. But much of software engineering means not knowing things and how to deal with that.
- donttrack 9y agoI would leave, if someone made me do pair programming.
- ben509 9y agoIt always seems to be something that's a great idea for somebody else to do.
- crdoconnor 9y agoWhy?
- hawaiianbrah 9y agoHave you ever practiced it? What’d you dislike so much? I’ve had great experience with it, and less than stellar ones too. It isn’t easy but it can be quite fun.
- razodactyl 9y agoThis is silly, you shut down the idea without any reasoning. I've found this a great way to get integrated into a new team and occasionally when banging heads against a wall trying to figure out an issue. In reality, pair programming happens very rarely but when it does it's very useful.
- donttrack 9y agoI also hate team building exercises, so there's that. Just let me go home.