What I have taught developers about writing
summary
Gives four concrete, testable rules for developer writing and shows them applied to a real engineering blog: start with the good stuff, keep it simple, write what people say, don't repeat yourself. Argues emotional hooks matter for engineers (supported by a quick poll of favorite movies), cites Chicago Manual of Style and Strunk & White for usage, describes a company email incident illustrating missing social skills, and reports the blog post was picked up by The Guardian.
AI-written summary · about
chapters (9)
- 0:00Developers should write better
- 2:34Two reasons developers write
- 4:23From nerds to tech leaders
- 11:06Social skills for tech stars
- 14:43New currency of smartness
- 16:07Engineering blogs less boring
- 18:10Four rules for tech writing
- 26:44Don’t be dumb and boring
- 27:57Q&A
related talks
16mWhat writing about frontend dev taught me about communicating with the world
31m7 Essential Tips for the Enlightened Tech Writer
31mThe Effective Developer - Work Smarter, Not Harder
44mWriting For Nerds - Blogging For Fun and (Not Much) Profit
33mWhat it takes to become a great developer!
50mThe Effective Developer - Work Smarter, Not Harder
27m'The Art of Software Development'
43mWrite an Excellent Programming Blog