2 ms·
read any hn thread about how much time software engineers spend working. big company programmers are putting in 6 hours of effort per week.
by dustingetz 5y ago
read any hn thread about how much time software engineers spend working. big company programmers are putting in 6 hours of effort per week.
- Tabular-Iceberg 5y agoMaybe that’s the point. It’s harder to just sit at your desk and space out when you’re right next to someone else. On the other hand I feel like pair programming sessions often get sidetracked into interesting conversations about technology or just about anything else that’s interesting, so that part is nice.
- JackMorgan 5y agoThis is the biggest thing I have seen with pairing when it works. People are less likely to disrupt a pair, but they'll happily bother a single person. Enough of those happen a week, and the pair gets 20+ hours of coding vs the two singles only getting six each.
- denton-scratch 5y ago> pair programming sessions often get sidetracked I've never experienced that. My experience was that pairing sessions were continuous, bloody hard work. My partner and I would have our noses to the grindstone throughout the session, which was strictly time-delimited (10AM to 5PM). I'd go home exhausted. Whether you're driving or navigating, you have to concentrate. The navigator has to show the driver that he's paying attention; the driver has to account for what he's doing. Working solo, it's much easier to get sidetracked. Feeling overloaded? Well, spend a few minutes on HN.
- mnsc 5y agoHow dare you call me out like that! But really, when you have trust rather than competition between colleagues it's absolutely ok to plan regular breaks and pull the emergency break when your focus juice has run out for the day. So depending on culture and how stable/jelled-in your team is pair programming shouldn't a exhaustive grind. That doesn't seem sustainable.