Yeah I really like the analogy to software. I noticed the parent comment said "separating these things into entities with specific concerns," which is almost ve

Yeah I really like the analogy to software. I noticed the parent comment said "separating these things into entities with specific concerns," which is almost verbatim the maximum of following Separation of Concerns in software design. We changed policy at my company from requiring one senior dev to approve pull requests to needing 2. Approvals went from nearly instant to taking much longer, and as a result we did start making longer PRs because of the nuisance of tracking down the second approval for very small changes. When I think about how congress needs 50+ senator approvals for any change to happen, it's no wonder to me that pork and riders became the standard.