Anti-patterns in software blogging
Points and comments are a snapshot, not live.
The author catalogs common writing and technical mistakes in software blogging, treating them as anti-patterns.
The article identifies seven anti-patterns in software blogging: the meandering intro, assuming the reader shares the author's knowledge, overreliance on links, sequel injection (assuming readers read prior posts), excessive formality, page overflow on mobile, and unreadable font. It recommends answering why the reader should continue within the title and first three sentences, minimizing reader assumptions, explaining terms on the page, avoiding sequel framing, writing conversationally, testing mobile layout, and checking contrast with browser tools. Examples from Joel Spolsky and a rewritten Docker intro illustrate effective alternatives.
What commenters are saying
Commenters largely agree that meandering intros and burying the lede frustrate readers. Some distinguish software blogs from Stack Overflow, noting LLMs have largely replaced the latter. A few push back against optimizing for engagement, arguing personality and genuine learning experiments (like Julia Evans' Nix notes) are more valuable than formulaic hooks. Another camp emphasizes the failure to connect new concepts to what readers already know, calling it more damaging than the meandering intro. The sequel and lack-of-expertise anti-patterns also draw supportive anecdotes.