Why senior developers fail to communicate their expertise

· ai · Source ↗

TLDR

  • Senior devs frame problems as complexity management; the rest of the business frames them as uncertainty reduction, causing persistent communication failure.

Key Takeaways

  • Two business loops run simultaneously: loop one (sales, marketing, product) hunts uncertainty reduction through speed; loop two (senior devs) hunts complexity management for stability.
  • The communication fix is a single reframe: stop citing maintenance costs and start asking “Can we try something quicker?” – speed language that still exercises the reduce/reuse instinct.
  • AI accelerates loop one but actively destabilizes loop two by worsening understandability, debuggability, and teachability while taking no responsibility.
  • Proposed structural response: decouple into a “Speed” system (AI, junior devs, fast iteration) and a “Scale” system (senior-reviewed, stable) – features ship on Speed, then get stabilized on Scale.
  • The senior developer role shifts toward editor over writer: extracting what works from the vomit draft rather than controlling what gets written.

Hacker News Comment Review

  • Commenters pushed back hard on the binary senior-dev archetype: the “avoider” framing breaks down in domains like firmware or safety-critical systems where adding complexity is sometimes the correct conservative move.
  • The tacit knowledge angle dominated the top thread – senior expertise is often inseparable from an internal world model that cannot be cleanly verbalized, making “just communicate better” advice structurally incomplete.
  • Several commenters noted the PoC-to-production trap undermines the Speed/Scale decoupling proposal: promised rewrites almost never happen once a prototype gains traction, collapsing both systems into the same unstable codebase.

Notable Comments

  • @hamstergene: frames the core problem as tacit knowledge – expertise lives in an internal world model that resists verbalization, not just vocabulary gaps.
  • @throwway120385: argues a competent senior reads the company’s current culture and its 5-year trajectory, adapting the complexity/speed dial rather than holding one fixed stance.

Original | Discuss on HN