3 ms·
Do people really want to work in pairs all the time? I feel like it would get tiring if not just an occasional thing. There's also value in being able to be an
by kcb 4y ago
Do people really want to work in pairs all the time? I feel like it would get tiring if not just an occasional thing. There's also value in being able to be an "individual contributor"
- mkl95 4y agoI'm OK with pairing a significant amount of time if it's async. I find traditional sync pairing draining after an hour or so. If you are pairing all the time something has to be off, it's not efficient at all.
- merlincorey 4y agoHow exactly is it still "pairing" if you are doing it asynchronously? My understanding and experience with "pairing" is that it pretty much has to be synchronous because generally at least two people should be looking at the same screen while generally one is providing inputs (mouse, keyboard) and the other is providing high level guidance and looking out for low level mistakes. Doing it asynchronously seemingly would not dispense with sharing the screen and one person handling inputs which seems like it would be even less efficient.
- marcosdumay 4y agoI imagine they mean when you work with some high bandwidth channel with another developer, and work independently on the same thing.
- dieselgate 4y agoOne type of async pairing I’ve done is “one person writes tests and the other writes the code to pass said tests - then swap” Im sure there are others but this is all I’m familiar with - it works ok and has the benefit of being sorta TDD, or at the least making sure tests are written
- wahnfrieden 4y agothis branch strategy works pairing or not