> * Redundancy (if you are on holiday or sick somebody else still knows the code deeply) This is the part I’m always puzzled by. I read and understand every li

> * Redundancy (if you are on holiday or sick somebody else still knows the code deeply) This is the part I’m always puzzled by. I read and understand every line of code my team merges in. If I don’t feel like I fully understand it, I ask questions, in code review. If I’m still not getting it I may ask for a zoom meeting. But that’s maybe once a week. Consequently I can jump in and manage issues or bugs pretty much anywhere in the product, and it’s fairly complex. I think there are two kinds of programmers, those who quickly read and understand code and those who more quickly understand from talking about the code, and these two groups will always talk past each other when discussing pair programming.