Ask HN: Examples of good technical writing?
I wonder if HN could share their favorite pieces of technical writing?
Preferably openly available content so that everyone can access (blogs etc.)
Focus is on "overall" score: tone, presentation, etc. as opposed to "very technically advanced" (although advanced examples fully welcome)
EDIT: awesome suggestions so far - should add that it doesn't have to be programming or even computer related... cookbooks count!
144 comments
[ 2.8 ms ] story [ 253 ms ] thread[p.s. RIP Pieter -> Read this: https://web.archive.org/web/20090420070511/http://www.digist...]
https://zachholman.com/talk/utc-is-enough-for-everyone-right
https://gutenberg.org/ebooks/55264
But as an example of good technical writing in general, I don't think it holds up so well. The style is extremely discursive and there is little structure except for the chapters, many of which are 50 page monoliths. So to me it's more like a work of literature that you take at the author's pace, not a useful repository of technical information for someone whose time and focus are more limited.
Don't get me wrong, I like texts that read well and gradually unfold into a deeper understanding of their subject matter, but in technical writing I also like support for a reader who needs to understand specific aspects of a subject in a form that is convenient to them as a student or professional
> I like texts that read well and gradually unfold into a deeper understanding of their subject matter
Sounds good! Will check it out.
Edit: formatting.
Over the past few years, Prisma has been quietly building a complete zero to advanced guide to databases that I've started to refer people to and use as reference myself. It stands out to me because it is focusing on a broader topic than what you typically find in docs, it's written simply, it is super comprehensive, and it's not trying to sell something.
Inside look at modern web browser (https://developer.chrome.com/blog/inside-browser-part1/) - fun illustrations
Nunjucks (https://mozilla.github.io/nunjucks/templating.html) - easy-to-use site nav
Vodafone + Core Web Vitals case study (https://web.dev/vodafone/) - packed with info and no marketing BS (disclosure: I was majorly involved in that content)
In the 1980s the children's publisher Usborne published computing books for young readers and a few years ago they made the books available for free download. The books use illustrations extensively to explain concepts. Not only are these books well written with clear, concise explanations, they are also more readable and enjoyable than many programming and computing books published for adults today.
Anyone writing a technical guide (of any kind) would benefit from reading these as a source of ideas and inspiration:
https://usborne.com/gb/books/computer-and-coding-books
1. You had to type the code in to get it working. There would inevitably be errors which I had to debug and fix that taught me that skill.
2. I had GW-BASIC on DOS while the book used another dialect and it had some "porting guides" in the appendix. I sort of learnt some lower level details from porting the programs to work on my computer.
I also feel that they had a friendly but "gloves off" approach to teaching. They treated their (child) audience as smart, intelligent, small adults rather than kids who needed to be entertained to learn anything and achieved something which, I feel, is missing in many modern books.
1. What was your mathematical knowledge when you read this book?
2. What did you gain from working through this book?
0: http://day8.github.io/re-frame/re-frame/
Other books by him.
1. The UNIX programming environment
2. The Practice of Programming
3. The Go Programming Language
The Go book was mostly written by Alan Donavan, according to Kernighan anyway (as stated in some interviews), but he's not the bragging sort so he might be underselling his contribution.
https://en.m.wikipedia.org/wiki/AWK
And Brian Kernighan has done a lot more than what I've read in this thread so far (though I've not read the full thing yet, and of course, it changes over time).
His overall influence on the field of software also extends far beyond his own direct work.
https://en.m.wikipedia.org/wiki/Brian_Kernighan
He is one of my top software gurus, since early in my career, since I worked a lot with Unix, from early on, but not only due to his Unix work and writing. I've used the knowledge and wisdom in some of his books to great advantage, throughout my career, and will be forever thankful to him and the rest of the early as well as later Unix "gang" for that.
The Elements of Programming Style
Software Tools / Software Tools in Pascal
I have read Elements and Software Tools in Pascal, and while partially definitely outdated ("avoid FORTRAN's three-way if"), excellent writing. Especially Software Tools in Pascal, which in large parts describes and explains source code; I was very impressed by the way the descriptions added lots of insights on top of just the code. Kernighan also manages to smuggle subtle bits of humour into texts about otherwise dry topics.
I enjoy clowning around and joking in personal interactions (if appropriate) and used to do it in my writing, but have come to believe that the humble, dry, concise style of the works mentioned above is most suitable and clearest for technical writing addressed to an unknown audience.
And, of course, Knuth.
I learned C from “Practical C Programming” by Steve Oualline. I remember reading it on bus rides home from work and just itching to try out the code myself. I loved that the author motivated many of the exercises with the weird corners of C that eventually bite you if you only have a naive understanding of the language. There’s even a fun one on the cover itself.
https://docs.racket-lang.org/
[0] https://www.boost.org/doc/libs/1_79_0/libs/math/doc/html/ind...
[1] https://scikit-learn.org/stable/
Here is another example, the manual for Microsoft Word 1.0 for DOS: http://toastytech.com/manuals/MS%20Word%201.00%20for%20DOS%2...
https://www.forth.com/starting-forth/ (PDF)
"why's (poignant) Guide to Ruby"
All right, this one is not purely technical. It's technical, but mixed with comics, art and a lot of personality.
It is an old classic in the community, and something that I aim up towards. Opened up my imagination to what a unique thing a technical book can become.
So many of these comments are recommending dry prose, Julia’s writing is fun and sympathetic about how hard all this junk is
I’ve found myself writing technical stuff in her voice a lot these days and I think it’s made my documentation more accessible
The PostgreSQL documentation is pretty fabulous. It’s well organized, complete, clear, and purposeful. You can read it like a textbook from page 1, or dive into it as a quick reference.
Emacs and Vim manuals.