It frustrates me the one size fits all approach often taken to software development best practices. If no one is to review the code, then all code is either wr

It frustrates me the one size fits all approach often taken to software development best practices. If no one is to review the code, then all code is either written by pairing/mobbing, or else it is the product of one persons thinking, blindspots, biases and all. It's great if you work in a team that pairs in everything, does trunk based development etc; that doesn't make it suitable for every team.