undefined | Better HN

0 pointsvundercind2y ago0 comments

If it’s regularly-scheduled rather than need-driven: then yes.

0 comments

done right it's terrible, done properly in the right team it's amazing.

it's just 1 work technique. but i've never been in a team where it felt like a meeting. you're literally writing code together, i've never done that in a meeting

vundercindOP2y ago

Done well but not on an as-needed basis, it bears a lost-productivity and energy-draining similarity to meetings.

Done poorly and not as-needed, it’s a living hell (but then, many business-things are when done poorly)

willsmith722y ago

where does your "as-needed" idea come from?

again, it's lost productivity and energy-draining when done poorly. it seems like you haven't experienced a team doing pair programming well, meaning full buy-in and pairing-trained.

some of the most productive teams i've been on worked 5 hours of pairing 4 days/week

1 more reply

j / k navigate · click thread line to collapse

0 comments

willsmith722y ago

done right it's terrible, done properly in the right team it's amazing.

it's just 1 work technique. but i've never been in a team where it felt like a meeting. you're literally writing code together, i've never done that in a meeting

vundercindOP2y ago

Done well but not on an as-needed basis, it bears a lost-productivity and energy-draining similarity to meetings.

Done poorly and not as-needed, it’s a living hell (but then, many business-things are when done poorly)

willsmith722y ago

where does your "as-needed" idea come from?

again, it's lost productivity and energy-draining when done poorly. it seems like you haven't experienced a team doing pair programming well, meaning full buy-in and pairing-trained.

some of the most productive teams i've been on worked 5 hours of pairing 4 days/week

1 more reply

j / k navigate · click thread line to collapse