4 ms·
As someone who worked in an all pairing shop for two years (run by a bunch of former Pivots), I can confirm it’s pretty draining, though my experience wasn’t ne
by naomiajacobs 5y ago
As someone who worked in an all pairing shop for two years (run by a bunch of former Pivots), I can confirm it’s pretty draining, though my experience wasn’t nearly as bad.
I actually liked pairing a lot of the time, and still think it’s an excellent way to onboard into a new code base, even in a non pairing shop (I even miss it sometimes!). For me, the main drawback after a while was that I felt like I was less efficient when pairing on stuff I knew how to do, and my personal growth as an engineer was stunted because I could always lean on a more experienced pair. Since that was my first eng gig, my second job had quite a steep learning curve as I had to figure out how to debug and navigate on my own, without talking through it out loud.
- thaumasiotes 5y ago> my second job had quite a steep learning curve as I had to figure out how to debug and navigate on my own, without talking through it out loud. Why couldn't you talk through it out loud?
- edem 5y agoSounds funny if you talk aloud while no one else is there.
- bloudermilk 5y agoThere’s actually a term for this: https://en.m.wikipedia.org/wiki/Rubber_duck_debugging https://en.m.wikipedia.org/wiki/Rubber_duck_debugging
- edem 5y agoI still have a blue rubber duck with "integer overflow" written on it. Got it many years ago but interestingly enough I never used it.
- naomiajacobs 5y agoWell, you can, but you'll annoy people even more than if you had a mechanical keyboard ;) I do have a little needle-felted rubber duck I keep on my desk while working, remotely, though, for just that reason.