4 ms·
Personally, I dislike PP - hard for remote teams. Only good if everyone on the team can easily pair up. - only good if everyone follows a strict schedule - o
by Justsignedup 7y ago
Personally, I dislike PP
- hard for remote teams. Only good if everyone on the team can easily pair up.
- only good if everyone follows a strict schedule
- only good if everyone understands the problem and solution space equally. If one of us needs to go into a cave for an hr to read documentation or experiment, it all falls apart.
- very mentally intense. You're always on. Can only keep it up for a few hrs without some massive mental drainage.
Overall I like PP for small problems to help teach someone. I dislike it for day-to-day.
- karatestomp 7y agoI find it really hard to try things I'm not sure will work, or noodle around, or feel my way toward a solution, when someone's watching. Just incredibly uncomfortable. Since those sorts of things are where a lot of my value comes from, count me out on PP. It's fine in very small doses for specific purposes when both people want it and are already comfortable working together but I'd go fucking crazy being forced to do it every day on a schedule.
- perlpimp 7y agoWhen you rapport between team members both of you will fill some blind spots.
- throwaway55554 7y agoI like PP when I am working on an established code base making changes. If I'm working on a PoC or something, I spend more time with pencil and paper up front than I do at a keyboard, so PP is out.
- odyssey7 7y ago> only good if everyone understands the problem and solution space equally That's a goal of pairing up. Together you'll get it better than you would have separately, if for no other reason than the one person who already knows it has to be able to explain it. And as a bonus, now that knowledge belongs to two people instead of being siloed with one of them.