Tutorial: Technical Blogging for Python Programmers
summary
Three simple rules anchor the tutorial: be lazy, be a reader, be a good accomplice. Concrete tactics include an editorial calendar and outlines that become an ebook, batching research with timers, clipping links into Evernote or Zotero, and feeding an RSS into MailChimp for email. Practical numbers: one person reports 12,000 words in a day and once wrote 40 posts in a month to schedule a year of content. Tech advice: use WordPress to avoid rolling a CMS (custom CMSs crashed sites and halved traffic), consider Flask‑Blog or Pelican later, and batch research to speed writing.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:04Why I Get to Talk About Blogging
- 1:37What's Happening Here
- 15:00Planning your content
- 16:59The Python ecosystem PP
- 28:21Prepping your research
- 39:15Posting checklist
related talks
44mWriting For Nerds - Blogging For Fun and (Not Much) Profit
30mWriting So Your Words Are Read
52mHow to Engineer Your Developer Blog Posts to Have Bigger Impact
33mHow to Write Useful Technical Texts
04mYou should write a blog post
05mBecoming an R blogger
31mWhat nobody tells you about documentation
52mTechnically Speaking: improve your code with documentation