Tech Tutorials
Tutorial viewers are stuck on a step. A comment that names the step and shares what worked gets read.
Where to comment
Comment on tutorials where a step is ambiguous, a tool choice is contested, or an edge case is skipped — and where you have run the step yourself.
What good looks like
Name the timestamp and the step, say what happened on your setup, and ask about the edge case the tutorial skipped.
Example draft
The step at 8:40 unblocked me — I had the volume mount backwards and the container kept starting empty. Do you mount the config file directly or the whole directory?
Edited version
The step at 8:40 finally unblocked me — I had the volume mount backwards, so the container kept starting empty. On your setup, do you mount the config file directly, or the whole directory? I am trying to work out which one survives a container rebuild cleanly.
Why it works
A timestamp plus a setup detail is immediately useful to the next person stuck at the same step, and it asks a question the creator can answer from experience.
What not to do
- • Do not paste error logs or ask the creator to debug your setup in a comment.
- • Do not recommend a tool you have not used, or claim a benchmark you did not run.
- • Do not comment on tutorials for tools you have never opened.
A weekly routine
Two tutorials a week in one stack. Comment only on steps you have actually run, and note the answers — they become your own troubleshooting library.
More free tools
PlaybooksFinance & Personal FinanceBeauty & LifestyleGaming CommentaryEducation & ExplainersCooking & FoodFitness & TrainingMusic & MusiciansTravel & JourneysPets & AnimalsPhotographyDIY & CraftsComment ScoreAI Comment Generator
Last updated: October 2026