Urgent.News

What's breaking now, across thousands of outlets.

Tech

Anti-Patterns in Software Blogging

The most frequent mistake in software blogging, by far, is meandering. Developers love to start blog posts with backstory, historical context, and whatever else happens to be on their minds. This may be enjoyable to write, but it's not always engaging for readers. In today's fast-paced world, readers have a multitude of articles to choose from.

They won't invest 20 minutes reading your post unless they believe you'll provide a payoff. The introduction of a blog post should answer the reader's two primary questions quickly: What value will this article provide? Why should I read it? A compelling introduction should clearly convey the article's relevance to programmers using the relevant programming language and outline the benefit of learning a new technique quickly.

While it's acceptable to include additional elements like a subtitle, bio, image, or famous quote, these elements consume the reader's limited attention and should be used sparingly. Effective teachers often compare new concepts to familiar ideas to help readers grasp the material. For example, when explaining Jellyfin, you might say, "Jellyfin is a streaming service like Netflix, except it's open-source and private, so nobody monitors your viewing habits."

When introducing Docker to developers who have never heard of it, the author compares it to a simplified front-end for Linux cgroups or jails in *BSD. Developers may not recognize Docker terms like cgroups, jails, or *BSD, or even understand what Linux is. To avoid assuming the reader's background knowledge, minimize assumptions about the reader's background.

Instead, provide a clear definition of Docker as a tool for creating consistent, reproducible environments for applications. Write your blog post with the target reader in mind, considering what they already know. List the terms they recognize and those they don't. Re-read your article, replacing technical terms with more accessible explanations if necessary.

Effective bloggers assume the reader is likely unaware of certain terms and provide explanations as needed. By minimizing assumptions and providing clear explanations, bloggers can create content that resonates with a wider audience.

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

Read the original at refactoringenglish.com →

More in Tech

Security updates for Wednesday

Security updates have been issued by AlmaLinux (bind, dovecot, freerdp, kernel, mariadb-connector-c, mod_auth_openidc, nodejs22, nodejs:22, sudo, and vim), Debian (node-shell-quote, puma, rails…

Sentiment analysis on YouTube comments with Python: handling sarcasm, emoji and spam

Comments are the cheapest audience research you have, and the hardest to read. A video with a few thousand of them is too many to skim, and a single sentiment score from a library will mislead you.

  • YouTube comment sentiment analysis is challenging due to noise and misinterpretation
  • Clean data by excluding creator comments, links, short comments, and duplicates
  • Validate tool against hand-labeled sample and adjust model or prompt as needed

The Matrix of Code Reviews: Why Tiny, Focused Pull Requests Are Your Red Pill

The Quest Begins (The "Why") Picture this: I’m staring at a pull request that touches twenty‑seven files, adds a new authentication flow, tweaks the UI, refactors a utility library, and somehow also…

  • Small, focused pull requests improve review speed and quality
  • One logical change per PR reduces cognitive load and bugs
  • Breaking features into smaller PRs enhances development workflow

More from Wednesday 7 October →