|
MediaSpurt
@MediaSpurt
|
16. sij |
|
Pair programming = 2x the cost and 1/2 the productivity
|
||
|
|
||
|
|
Franky
@FrankyPelvis
|
16. sij |
|
It’s debatable, having a second brain to bounce ideas off can be great early on in design or refactoring, but for me it has diminishing returns. I wouldn’t want to do it for everything.
|
||
|
|
||
|
Quid Pro Ho
@_andrewmartin_
|
16. sij |
|
This is going to sound stupid. But because I come from a violin/music theory/philosophy background before tech, I see coding as a deeply personal, private, and artistic process. I'm not saying that makes me actually good at any of this. But that's my day-in day-out joy.
|
||
|
|
||
|
Caitlyn Landry
@caitlynlandry
|
16. sij |
|
I paired almost every day at my last job and it was exhausting, now I almost never do and I miss it, so yeah, moderation.
|
||
|
|
||
|
Matthew Weeks
@MWeeksDev
|
16. sij |
|
It's a lot of pressure, but it can be so rewarding when you're in sync as a pair!
|
||
|
|
||
|
James
@James_Neale
|
16. sij |
|
I think it works best when both people are very good at what they do, absolutely respect each other, can debate without being offended, and can understand and accept other ideas. Productivity is on par or greater overall, but biggest reward is quality of product and less bugs.
|
||
|
|
||
|
Glenn Stovall
@GSto
|
16. sij |
|
people DO that !? on purpose?
|
||
|
|
||
|
Matt Greer
@mattegreer
|
16. sij |
|
I worked at a company that 100% pair programmed. So glad I don’t work there anymore :)
|
||
|
|
||