How to Engineer Your Developer Blog Posts to Have Bigger Impact
summary
Argues that empathy as true north beats clever prose: design for skimmers with H2 section headers, bold-start bullets, diagrams, alt‑text and footnotes. Recommends an iterative edit cycle (first drafts allowed to suck), reading drafts aloud, checklists and a “cutting room floor” for deleted bits. Optimize titles and anchor text for SEO; splitting one long draft into three shorter posts sends each to front‑page Hacker News. Syndication to Planet Postgres drives real reach — one tweet gets ~9,000 views.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker background
- 2:54Writing content for impact
- 19:17Editing cycle and first drafts
- 29:42SEO and discoverability tips
- 39:15Promotion and distribution strategies
- 47:22Community resources and closing
related talks
04mYou should write a blog post
44mWriting For Nerds - Blogging For Fun and (Not Much) Profit
43mWrite an Excellent Programming Blog
31mHow To Write About Software
31mThe Effective Developer - Work Smarter, Not Harder
16mWhat writing about frontend dev taught me about communicating with the world
43mWhy You Need to Think and Act Like an Editor
22mBoosting Your Blog's Visibility: Strategies to Drive More Traffic and Engagement