Writing a perfect technical tutorial
summary
Shows the actual authoring workflow: starting from code notes and a Markdown baseline, followed by a review schedule and who to include. Gives concrete examples and tools used—Twitter API to Google Sheets, pandas, Google Sheets scripts, AWS Amplify, AutoML and Twilio, GitHub Actions—and reports outcomes: traffic, repo clones, PRs and one tutorial that inspired six posts. Explains how success is measured (people who built things, support links) and how to keep code current so the tutorial still works.
AI-written summary · about
chapters (20)
- 0:00Start
- 2:06Why write a tutorial?
- 3:33What makes a good topic • A topic that's been coming into support often • Anything you got stuck on • Something you are excited about • Anything that you built that you are proud of
- 5:56Where do you want to publish this tutorial?
- 6:53What is the goal of your tutorial?
- 7:12What do you want the reader to walk away with?
- 8:13What is the story you are trying to tell?
- 8:37Create a baseline that you can refine and build into a tutorial
- 10:02Does your code have a narrative structure?
- 10:37I use a markdown file while I am writing a code sample that I can edit later on
- 11:03I've also used a screen recorder to record myself writing code and used that to create my baseline
- 11:27Examples
- 11:57Sending a response from the Twitter API to a spreadsheet in Google Sheets
- 16:30Review process
- 16:59Try to find reviewers who a mix of your peers and subject matter experts
- 17:42Do you know anyone who is part of the audience you are trying to reach?
- 18:55Be mindful of your overall vision during this part of the process
- 20:26After you publish your tutorial
- 22:23Refreshing your tutorial as it gets out of date
- 25:19Conclusion
related talks
01h 14mTechnically speaking: Improve Your Code With Documentation
39mTackling Technical Writing
43mUseful and Beautiful Developer Docs and How to Create Them
29mDocumentation: The Missing Pieces
13mTechnical documentation – how can I write them better and why should I care?
46mSave a Dev, Write Documentation!
35mThe Art of Documentation and Readme.md for Open Source Projects
52mTechnically Speaking: improve your code with documentation
