The social layer

The most inefficient part of building software is other people.

Not the compiler. Not the legacy codebase. Not the deployment pipeline with the flaky test on step seven. People. Misaligned context, coordination gaps, the meeting that could have been a message that could have been a decision that never got made.

This is not a bug in the system. It is the system.

The only recourse is tolerance, compassion, empathy, patience. Not as soft skills you list somewhere between "team player" and "self-motivated." As disciplines you practice daily. The rate-limiting step isn't the code review. It's whether you can explain your reasoning to someone under different pressure than you, without contempt, without condescension, without implying they should already know this.

You can't merge the branch of a relationship. There's no rebase for a trust deficit.

None of this shows up in any metric. Not an accident — the metrics were designed by people who believed the social layer was overhead. Coordination cost to minimize. They were wrong, and the evidence is in every post-mortem that lists "communication breakdown" as a contributing factor and then adds another process instead of addressing the actual thing.

Process is not the skill. The skill is the skill.

There's no shortcut. You can't automate patience. You can't hire your way out of the need to understand someone else's context. The social layer isn't the obstacle between you and the real work.

It is the real work.

We're all we've got.