The Miller Principle
FelipeCortez's 'Miller Principle' boldly declares that 'No one reads anything,' specifically targeting documentation, code comments, and lengthy emails. This provocative hot take resonated deeply with the HN community, sparking a lively debate about the value of good documentation and the emerging role of AI in information consumption. It's a cynical yet relatable observation that challenges common assumptions about how we interact with written information in the tech world.
The Lowdown
The Miller Principle, coined by FelipeCortez, asserts a seemingly universal truth: 'No one reads anything.' This short, incisive observation highlights a core frustration in many professional and technical environments, suggesting that efforts put into detailed written communications often go unrewarded.
- User Documentation: Despite its critical role, user manuals and guides are frequently skipped.
- Specifications: Detailed project or technical specifications often remain unread by those who need them most.
- Code Comments: Inline explanations, intended to clarify complex logic, are overlooked.
- User Interface Text: On-screen instructions or descriptive labels are ignored by users eager to proceed.
- Long Emails: Any email extending beyond a single line is likely to be skimmed or completely disregarded.
The principle, delivered with a touch of humor, implies that our collective attention spans are shorter than ever, forcing communicators to rethink how they convey information effectively.
The Gossip
Reading Rebuttals
Many commenters quickly challenged the Miller Principle, asserting that they indeed read various forms of documentation. They highlighted the immense value found in well-structured and comprehensive resources like Python, SQLite, Arch Wiki, or Laravel's guides. The consensus was that while poorly written or unnecessary text goes unread, high-quality documentation is indispensable for learning, debugging, and future reference, often written for one's 'future self.'
LLM Literacy
The advent of large language models (LLMs) injected a new dimension into the discussion. Commenters mused that if humans aren't reading, AI agents are, consuming 'everything.' This raised questions about who the intended audience for documentation might become, and the practical implications for developers who, despite using AI tools, still find themselves needing to consult original, reliable documentation because LLMs can generate outdated or incorrect information.
Email Exhaustion
The inclusion of 'any email longer than one line' in the Miller Principle resonated strongly. Many shared their frustration with verbose and unstructured emails, particularly from colleagues. The common coping mechanism involves skimming for key phrases or simply asking for a summary. This underscores a widespread professional communication challenge, where brevity and clarity in email are often preferred but rarely delivered.