3 HN users recommended this talk3 months2021–2024score 3.5
Years with an HN recommendation, 2007–2026
HN recommends it as the best concise introduction to a practical framework for structuring documentation, the basis of what became Diataxis.
Daniele Procida's PyCon AU 2017 talk presents a system that divides documentation into four kinds, usually drawn as four quadrants. He explains why mixing them makes docs poor and how separating them improves writing.
“I highly recommend Daniele Procida's talk about this” (HN, 2021)
Related to this: understanding the various types of documentation, and using them all appropriately. I highly recommend Daniele Procida's talk about this, [0] and the accompanying web page [1]. He gives a useful taxonomy of the 4 kinds of documentation. Through the power of Unicode: ┌──────────────────────────┬─────────────────────────┐ /\ │ Tutorials │ How-to Guide │ || Practical │ (Learning-oriented) │ (Problem-oriented) │ || ├──────────────────────────┼─────────────────────────┤ │ Discussions │ Reference │ || │ (Understanding-oriented) │ (Information-oriented) │ || Theoretical └──────────────────────────┴─────────────────────────┘ \/ <=== Useful for study Useful for coding ===> [0] [this video] (that will take you to the start of the talk proper) [1] [link] edit Didn't spot the link to [1] at the bottom of the article :P
____Response to Article____ Engineers are rarely good at writing technical documentation, especially compared to technical writers (that is “secretaries” per author’s lingo) which by definition, should be. Engineers generally cost more than technical writers. Good technical writing saves engineering time both during AND after the documentation is produced. Author spends large amount of time, to poorly express that to be a good technical writer, you must understand who needs what and why, then figure out how to solve that the best way based on the context. ____System for to Producing Tech Docs____ Anyone looking for a good system of producing documentation should check out: [link] Which has a 30-min presentation: [this video] Prior HN posts on the system are here: [link]
To be a good technical writer, you must understand who needs what and why, then figure out how to solve that the best way based on the context. Anyone looking for a good system of producing documentation should check out: [link] Which has a 30-min presentation: [this video] Prior HN posts on the system are here: [link]
They’re officially related. Personally, prefer the link I used since it provides a table of contents and link to this YouTube presentation on the system: [this video]
I'm a little less than impressed by the presentation here. The idea that Divio is describing here is the Diataxis framework ( [link] ), which "is the work of" ( [link] ) Daniele Procida ( [link] ). Who, incidentally, is also giving the PyCon talk in the video on the page you linked ( [this video] ). But I don't see anything resembling attribution for the ideas. They aren't just common industry knowledge or "received wisdom". (And the "quote" from David Laing at the top isn't really accomplishing anything, either.)
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
Plays via YouTube's privacy-enhanced embed
6 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Read more
Read more
Citations, criticism and jokes