liveBook · Manning

Blogging

As explained in Writing for Developers: Blogs that get read

The practice of publishing written entries on a blog to communicate information to an audience.

Blogging turns a recurring explanation into a durable resource: write the critical points clearly once, then link to the post instead of repeating them. section 1.1.10

Reuse a post wherever the same context is needed:

  • Answer new-hire questions, colleague confusion, or user questions with a link. section 1.1.10
  • Reference it from user documentation, commit summaries, code review comments, problem reports, forums, and social media. section 1.1.10
  • Update the post when your understanding changes, rather than synchronizing many separate messages. section 1.1.10

One explanation, many uses

Document a technical topic, then reuse that post in onboarding, project documentation, a code review, and a later article. Blogging can also support presentations, mentoring, professional connections, and career opportunities. section 1.1.10 section 1.2

Treat blogging as a communication and reputation practice, not a guaranteed income stream: paid newsletters and bestselling technical books are described as exceptions. section 1.1.11

How Writing for Developers: Blogs that get read covers it

How deep it goes
Explains reuse, reach, updating, and professional effects, but does not provide a detailed publishing workflow.
Examples
Uses onboarding answers, user docs, commit summaries, project descriptions, presentation notes, and Hacker News posts as examples.
What you can do after
Apply it by writing one clear explanation and linking it wherever the same technical context recurs.
How it connects
Connects blogging with documentation, code review, social media, public speaking, mentoring, and professional networking.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Writing for Developers: Blogs that get read. The section links point to the parts of the book it draws on.