Anti-patterns in software blogging
Software and developer blogs are increasingly criticized for “meandering intros,” buried ledes, excessive links-as-homework, and tutorials that assume readers know “everything except this one thing.” Commenters argue that good technical writing should foreground the key idea, clearly state prerequisites, respect the reader’s time, and be explicit about the author’s level of expertise—while still allowing room for personality and storytelling when appropriate to the audience. The thread also probes how large language models are displacing Stack Overflow–style Q&A, raising the stakes for human-written posts to provide genuine insight, context, and up‑to‑date guidance rather than AI-like slop.
Meandering intros & storytelling
- Many commenters dislike long, suspenseful intros in technical pieces; they want the core point and value proposition early (“don’t bury the lede”).
- Others argue storytelling can aid engagement and understanding, especially when readers are in “learn + entertainment” mode rather than task-focused troubleshooting.
- Several distinguish between formats: bug-hunt or narrative posts can sustain more story; tutorials, references, and news should be direct.
- There’s concern that “write each sentence only to keep the reader reading” can become clickbait, engagement bait, or “AI slop,” unless anchored in genuine value.
Audience, purpose, and style
- A recurring theme: everything is contextual. Good structure depends on audience (HN-style SWE, PhDs, casual learners, hobbyists) and intent (teach quickly, provoke thought, entertain).
- Some prefer neutral, matter‑of‑fact prose; others like strong personality. Overly casual or overly formal can both be off‑putting, depending on taste.
- Writing advice is seen as guidance, not law. Multiple people stress “take all rules with a grain of salt.”
Beginner vs expert voice & authority
- A major anti-pattern: “I did it once, now I’m an expert.” Readers object when tentative weekend experiments are presented as authoritative best practice.
- Many still want beginners to write, but to clearly frame posts as notes, experiments, or partial understanding.
- Good practice: share uncertainties and open questions explicitly, rather than overgeneralizing from a single experience.
Links, prerequisites, and maintenance
- Overreliance on links without summaries turns posts into “homework forests.” Summarizing linked concepts or quoting key parts is preferred.
- A key failure mode is assuming “the reader knows everything I know except one thing.” Readers want comparisons to familiar tools and clear motivation.
- Outdated tutorials (e.g., for old framework versions) are a common frustration; suggested fixes include updates or explicit obsolescence notices.
LLMs, Stack Overflow, and value of blogs
- Some say LLMs have largely replaced Stack Overflow and many dev blogs for quick answers; others ask where LLMs will get fresh, high‑quality knowledge if forums and blogs decline.
- Several still see strong value in blogs: deeper context, personal perspectives, and as a thinking tool for the writer.
- There’s noticeable distrust of LLM-generated posts, perceived as verbose, generic, and often low on substance.
Personal blogs vs productized content
- One camp: a blog is personal; there are no “anti-patterns” if the writer isn’t optimizing for growth or readership.
- Another camp: even for personal sites, bad writing patterns still exist, especially if posts are widely shared and influence community practices.