|
|
|
|
|
by wowokay
1568 days ago
|
|
I am of the same mind, I found value in pairing on small tasks, or maybe a code review/training, but generally I find it promotes 2 negative concepts. 1. That all developers can do/produce the same results. 2. That some people become dependent on others to write code. #1 fuels the management misconception that hiring or moving devs will result in more work getting done. #2 makes some individuals short change the PR review process. (I.E I was there when it was written, or I trust that pair thought through all the steps. I think it’s great in a lot of situations, where something new is being started or for KTing, but as a daily practice it reminds me of those old school group projects where 1 person does all the work and the other gets the credit. |
|