|
rotor posted:its basically a live 2 way code review Truman Peyote posted:exhausting is a really accurate term for it. i do think you get good code out of it and it's really great for teaching/learning. but i absolutely cannot do it for more than like an hour both of these have been my experience. the driver writes the code while the navigator serves as a rubber duck and maybe points out the occasional blind spot. frequently useful, but i wouldn't want it to be the only way i write code never tried swapping roles every few minutes. that just sounds like a great way to gently caress up both people's trains of thought
|
#
¿
Nov 18, 2021 00:07
|
|
|
|
| # ¿ May 15, 2024 05:00 |
|
|
rotor posted:navigator also looks up api docs that the driver will need in a little while so when they get there it's just "its getWidget and it takes a string name and an int id and the property hash we just built" oh, yeah. i frequently have docs open in a tab when i'm navigating i should also note that 99% of my pair programming has been over a screen share in a slack call or something similar, not two people sitting at one computer
|
|
#
¿
Nov 18, 2021 00:25
|
|
|
man in the eyeball hat posted:i had a good pair session right when i started my current gig. my boss, the guy who wrote all the code before i joined, was walking me through some profiling and basically rubber ducking each other on how to speed it up. it helped me to see how he wanted things prioritized in the code and to get my bearings in a codebase written by one guy. wtf, i don't remember posting this srsly tho, i can also think of examples where pairing benefited the senior. in one case, the junior innocently posed a question that brought an architectural weakness to the senior's attention. narrator's voice: datroof was the senior
|
|
#
¿
Nov 18, 2021 04:30
|
|
|
QuantumPotato posted:i briefly worked on a team where the engineering director was like the mad hatter of software management. whatever hackernews article hoved into his vision was the NEW, MANDATORY PRODUCTIVITY IMPROVER. so for about 3 months, every dev who reported to this dude was required to pair, with an assigned partner, for 6 hours a day, swapping every 20 minutes at maximum. My partner and I played TDD red light, green light (A writes a failing test, B implements the minimum for the test to pass and writes the next failing test, A implements next minimum, writes next test, repeat ad infinitum) for most of that time. first impression: that sounds like absolute hell second impression: that might actually work well in certain circumstances, for certain tasks tell me if i'm wrong, but if your team was even kinda functional, i'd guess that process stopped being mandatory after a couple weeks but still happened organically on occasion
|
|
#
¿
Nov 18, 2021 05:26
|
|