Related posts
Jon Seager
Blog
Revitalising Ubuntu Project Documentation
documentation outlining revamp
The subject this post names, from the same vocabulary
the directory files beliefs under, and the words it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
Sources
All Writing Blog GitHub Mastodon x.com Bluesky Korrents Recommends Site Papers
Top people
Julia Evans
Yoshua Bengio
Alice Ryhl
Daniel Stenberg
Duncan McClean
Matt Birchler
Elio Struyf
Brett Terpstra
Jason Fried
Ryan Singer
Patrick McKenzie
Hadley Wickham
Showing Profile →
Show everything
Hiding Show them again
Show them again
Further back ↓
Hiding Show them again
19 September
Designer, product manager, YouTuber and developer who has written about technology at Birchtree since 2010. He makes the Quick Reviews and Quick Notes apps and the A Better Computer YouTube channel.
17 September
Belgian engineering lead, Microsoft MVP and public speaker. Creator of Front Matter, a headless CMS extension for Visual Studio Code.
14 September
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
poll: to look up the official documentation for "git pull", would you use: (you can pick more than one) documentation Related
12 September
Mac developer and writer at brettterpstra.com; makes the apps Marked and nvALT and writes extensively about Markdown and automation.
11 September
Co-founder and CEO of 37signals, makers of Basecamp and HEY; co-author of Rework, Remote and It Does Not Have to Be Crazy at Work.
A really lovely GRID VIEW is coming to Basecamp 5 shortly. We had a grid view in 4, but it wasn't any good and I didn't want to drag it into 5. Had we done that, we'd have called it done and never revisited. By intentionally leaving it out, we allowed pressure to build to bring it back. And with no legacy to battle or revamp, we were able to return to the drawing board and make something so much better, from scratch. Coming to a Basecamp near you. Soon. Related
7 September
Author of Shape Up; formerly head of strategy at Basecamp, where he worked on product design for seventeen years; now runs Felt Presence.
The 7+/-2 rule never fails. I thought I was ready to kickoff something we shaped. But putting it through my documentation process felt hard. Why? Oh yeah. Missing a level of chunking. Suddenly way easier to talk about w/ both the team and agents. documentation Related
2 September
Writer on the intersection of technology and finance. Author of the Bits about Money newsletter and host of the Complex Systems podcast; previously at Stripe.
Being willing to read the documentation is a superpower, and I don’t think it becomes less of one in a world where technological or social changes make it rarer. documentation Related
31 August
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
I'm working on phase 2 of Project Improve Git's documentation and I need beta readers! Here's a signup form: https://forms.gle/swn1jhCULndnCxG87 The first topic is going to the docs on merge conflicts. I'd love signups from anyone who uses Git on the command line and who would be interested in reading the current version of some man pages and leaving feedback about what's confusing. Especially if you're not 100% comfortable with Git! documentation Related
Statistician and Chief Scientist at Posit (RStudio). Author of the ggplot2, dplyr and tidyverse R packages and of books on R programming and data science.
21 August
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
poll: do you prefer examples with: (you can pick more than one, trying to think about what my opinions are about the use of placeholders in examples) EDIT: please no more comments about the official recommended values for ip addresses and hostnames in documentation, try to think about that as a separate question documentation Related
20 July
Deep-learning researcher and Turing Award laureate; founder of the Mila institute.
3 June
Engineer and teacher; wrote Kubernetes the Hard Way, was a distinguished engineer at Google Cloud, and retired from full-time work in 2023.
documentation
Their words
I'm watching people write these huge markdown files to give the agent context. How about you write documentation to give me context so I can have fully working examples.
Show the whole quote
youtube.com
20 May
Rust engineer at Google working on Android; maintains Tokio and works on Rust in the Linux kernel.
From one piece
Why Rust is different, with Alice Ryhl
2 beliefs, in the piece's order there
documentation
Their words
Now the thing is you can of course write examples in your documentation and Rust makes all examples into tests. This means that if you change the underlying code now your test fails. And so this means that you can't even you can't forget to update your examples in your documentation.
Show the whole quote
Why Rust is different, with Alice Ryhl youtube.com
documentation
Their words
And what this is is that in the guide level explanation, you explain your feature as if you were writing a guide as if the feature already existed. And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial.
Show the whole quote
Why Rust is different, with Alice Ryhl youtube.com
8 May
Freelance web developer and instructor. Author of the Dive Into Docker course; writes tutorials on Docker, deployment and development environments at nickjanetakis.com.
30 April
Web developer; former head of engineering at Flickr, author of Building Scalable Web Sites, and co-founder and CTO of Slack.
20 March
Founding member of OpenAI and former director of AI at Tesla; creator of nanoGPT and the term "vibe coding".
documentation
Their words
It used to be that you have documentation for other people who are going to use your library, but like you shouldn't do that anymore. Like you should have instead of HTML documents for humans, you have markdown documents for agents.
Show the whole quote
youtube.com
10 March
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
1 March
Programmer; wrote Redis and hping, and blogs about C, systems programming and working alone.
18 February
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
Notes on clarifying man pages Hello! After spending some time working on the Git man pages last year, I’ve been thinking a little more about what makes a good man page. I’ve spent a lot of time writing cheat sheets for tools (tcpdump, gi…
documentation Related
12 February
Founded PSPDFKit in 2011 and ran it for a decade. Came back from a break to work on AI agents — the OpenClaw project, and OpenAI, joined in February 2026. Writes at steipete.me.
documentation
Their words
That's why I warn in my security documentation, don't use cheap models. Don't use Haiku or a local model. Even though I, I very much love the idea that this thing could completely run local. If you use a, a very weak local model, they are very gullible. It's very easy to, to prompt inject them.
Show the whole quote
youtube.com
5 February
Engineering leader and writer; wrote An Elegant Puzzle, Staff Engineer and The Engineering Executive's Primer, and blogs at Irrational Exuberance.
18 January
Machine learning engineer and independent AI consultant. He writes about LLM evaluation, tooling and applied ML at hamel.dev, and previously worked on machine learning at GitHub.
8 January
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
4 January
Swedish open source developer; creator and lead maintainer of curl and libcurl, and a co-founder of the Rockbox project.
16 October 2025
Swedish open source developer; creator and lead maintainer of curl and libcurl, and a co-founder of the Rockbox project.
27 September 2025
Programmer and teacher; writes on software, learning and the web, and makes the Coding Blocks video course.
Examples are the best documentation When I'm searching for docs, 95% of the time a single example would suffice. Yet, 95% of the time I can't find one in any official source. It seems that by default formal technical documentation is targeted towards some…
documentation Related
9 September 2025
Writer and consultant on formal methods and software correctness; author of Practical TLA+ and Logic for Programmers.
25 May 2025
Co-creator of Django and creator of Datasette; writes daily at simonwillison.net.
Their words
I still think Anthropic have the best prompting documentation of any LLM provider.
Show the whole quote
simonwillison.net
15 July 2024
Scottish software developer on the Statamic core team; runs a one-person business maintaining Statamic addons such as Runway and writes at duncanmcclean.com.
5 July 2024
Swedish open source developer; creator and lead maintainer of curl and libcurl, and a co-founder of the Rockbox project.
1 March 2023
Deep-learning researcher and Turing Award laureate; founder of the Mila institute.
17 January 2023
Writes jvns.ca, turning "hard and scary" topics — networking, debugging, Linux internals — into plain explanations and hand-drawn comics. Publishes Wizard Zines, illustrated programming zines. Software developer based in Montreal.
Their words
the Go standard library documentation is probably my favourite language reference
Show the whole quote
jvns.ca
28 May 2022
Indonesian software engineer, educator and engineering manager at Zero One Group; open-source enthusiast writing at ripandis.com.
Their words
System for notes, knowledge base, and project management. Helps organize and store references, documentation, and roadmaps.
Show the whole quote
ripandis.com
19 February 2022
Scottish software developer on the Statamic core team; runs a one-person business maintaining Statamic addons such as Runway and writes at duncanmcclean.com.
1 May 2020
Medicinal chemist; has written In the Pipeline, the drug-discovery blog, since 2002, and the “Things I Won’t Work With” posts about chemicals that try to kill you.
4 February 2020
French software engineer, public speaker and fully remote nomadic worker; writes about frontend development at maxpou.fr.
8 April 2019
Software engineer who writes the blog Made of Bugs about performance, debugging and understanding computer systems. Previously worked at Anthropic on interpretability, at Stripe on Sorbet, and at Ksplice.
Their words
This is far and away the best general-audience technical documentation of the Apollo missions I've read.
Show the whole quote
blog.nelhage.com
27 June 2017
Rust engineer at Google working on Android; maintains Tokio and works on Rust in the Linux kernel.
27 January 2017
Web developer and musician; co-creator of the Django web framework, founder of EveryBlock and of the music-notation site Soundslice.
12 March 2015
Maintainer of Git, the distributed version control system, since Linus Torvalds handed him the project in 2005.
Their words
Since the project I work on is a command-line tool that is primarily implemented in C, I use the usual CLI development tools, e.g. make, gcc, gdb, etc. The documentation is in AsciiDoc.
Show the whole quote
usesthis.com
11 May 2010
Programmer and entrepreneur; co-founded GitHub and created Jekyll, Gravatar and the Semantic Versioning spec.
Nothing matches. Show everything
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com .
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
Got it
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.
Got it