When moving fast, talking is the first thing to break

The thesis

Web veteran Dave Rupert argues that when "moving fast" becomes the overriding value in projects and organizations, communication is the first casualty. Conversations get cut; consensus gets bypassed. The result, he warns, is teams making unilateral choices—new folders, forked Figma components, ad-hoc codebases—that sprout into incompatible mini-systems. It has been reported that Rupert frames this not as theoretical hair-splitting but as a practical pipeline to messy merge conflicts and accumulating technical debt.

The consequences

Speed without conversation, the post contends, erodes shared systems: design systems, the canonical codebase, documentation, even security and reliability. Want to ship something fast? Fine. But whose work are you stepping on? The author points to a human cost too — developer satisfaction and cross-org collaboration get chipped away — and alleges that AI tools only make the pattern easier. Why ask an expert when an LLM will happily hand you what you want? Short-term wins, longer-term headaches.

Slow down — intentionally

Rupert's plea is blunt: reduce bullshit and toil, yes — but slow the hell down when needed and actually talk before you pull the trigger. That’s the emotional core of the piece: this isn’t nostalgia for meetings, it’s a call to preserve the shared fabric that lets teams row together. It’s an argument that engineering management should prioritize alignment and user value over churny feature count. Sound familiar? It echoes the old "move fast and break things" debate — only this time the prescription is less breakage and more listening.

Sources: daverupert.com, Hacker News