Lightning talks - Day 2
summary
Quick specifics: a five‑minute sketching workflow uses lines and boxes plus paper pens and a wall to iterate cheap ugly ideas before prototyping; error messages should state what went wrong/why, the consequences, and actionable fixes, avoid apologies and link to docs; a service called Dor renders templates (from GitHub or forms) to generate Sphinx projects on demand — server side templating that returns files; documentation culture at one company uses Confluence plus a conditional content macro and a versioning plugin to mimic feature branches; pick a beginner language with local support — community matters.
AI-written summary · about
chapters (6)
- 0:00Sketching
- 5:11Focus on users
- 8:35Documentation automation
- 13:44Documentation communication
- 21:51Conditional content
- 24:49Learning to program
