Expert Lenses — disagreement is knowledge¶
March 10, 2026 · LinkedIn
8 reactions · 2 comments · 658 views
Every team has seniors who see code differently. One always pushes for smaller, more focused components. Another asks "will this hold up under load?" Same PR, different concerns — both legitimate.
We usually resolve these tensions in meetings or PR threads. The decision survives. The disagreement disappears. And with it, the most valuable part: the reasoning.
We've been encoding expert lenses as Claude Code skills. Not style guides. Not linting rules. The actual worldview of a senior person — built from their PR comments, from interviewing them on what triggers a pushback, from extracting the vocabulary they reach for when something feels wrong.
A single lens is useful. It scales one person's judgment across every review they can't attend.
But here's what I didn't expect: two disagreeing lenses on the same code are more valuable than one.
The tension becomes visible before anyone walks into a room. You can see exactly where the lenses agree — probably fine — and where they diverge. That's where the real decision lives.
Junior developers stop learning rules. They start learning trade-offs.
Knowledge transfer has always tried to capture what was decided. Expert lenses capture how experienced people decide differently — and why both can be right.
The disagreement is the knowledge.