Urgent.News

What's breaking now, across thousands of outlets.

Tech

Anti-Patterns in Software Blogging

Anti-Patterns in Software Blogging Some excellent writing advice from Michael Lynch. Michael warns against "meandering intros", misjudging your reader's existing knowledge, assuming they'll read your previous posts, and excessive formality. He also warns against overreliance on links as an excuse not to explain terminology. This one hurt! I do this all the time, but I have a nagging suspicion…

In the realm of software blogging, certain pitfalls have emerged that hinder effective communication. Michael Lynch, a seasoned writer, offers valuable guidance on what to avoid. He cautions against long, convoluted introductions that fail to capture the reader's interest. Another common mistake is underestimating the reader's prior knowledge and presuming they will recall details from earlier posts. A formal tone is also discouraged, as it can alienate the audience.

Furthermore, Lynch warns against an excessive reliance on hyperlinks as a crutch, implying that explaining technical terms is unnecessary. This approach may be convenient for the writer, but it can frustrate readers who are unwilling or unable to follow every link. A Lobste.rs commenter clarifies Lynch's stance, stating that the article should remain intelligible even if readers skip the links. This principle ensures that the content remains accessible to a broader audience.

A crucial aspect highlighted by Lynch is the importance of using one's unique voice. Many novice bloggers fall into the trap of believing they must adopt a stiff, overly formal writing style to establish credibility. However, he emphasizes that writing in a conversational manner is far more engaging for readers. With an increasing trend of developers delegating their writing tasks to AI, software blogging risks becoming monotonous and lacking individuality. Readers yearn for content that reflects the writer's personality and perspective.

Simon Willison, a software developer, exemplifies this perspective through a link post dated October 7, 2026. In his post, he solicits support through a $10/month subscription, promising readers a monthly digest of significant developments in large language models (LLMs). By adhering to Lynch's advice, Willison aims to produce writing that stands out in a crowded field, attracting readers seeking fresh perspectives and engaging content.

Written by urgent.news from Simon Willison's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at simonwillison.net →

More in Tech

Nodejs Queue Publish for Offline Users: 12-Minute Live Poll Notifications

Nodejs Queue Publish for Offline Users: 12-Minute Live Poll Notifications Short answer: in a Nodejs-style service, queue the result before you publish it so offline users still get notified.

  • Queue events before publishing to ensure delivery to offline users
  • Use per-recipient inbox with idempotent fan-out for strong delivery evidence
  • Implement client acknowledgements or durable cursors for proof of notification visibility

I benchmarked seven hotel price APIs on the same Rome room, and the prices were 16% apart because of tax

I run FlightPowers, a small API that reads live Booking.com rates, so I'm biased about one row of this table. I wanted to know how it holds up next to the APIs people usually compare it with, so I…

  • Seven hotel price APIs benchmarked for same Rome room
  • 16% price discrepancy found among APIs, primarily due to tax differences
  • API choice and market sourcing significantly impact final price

More from Wednesday 7 October →