Related posts
documentation converts linking
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 x.com Mastodon Korrents Recommends Papers
Top people
Julia Evans
Alice Ryhl
Ryan Singer
Varun Raj Manoharan
Rakhim Davletkaliyev
Matt Birchler
Elio Struyf
François Chollet
Brett Terpstra
Andrew Gelman
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.
16 September
Author of Shape Up; formerly head of strategy at Basecamp, where he worked on product design for seventeen years; now runs Felt Presence.
If you need one definition of "experience design" it's this. Experience happens moment by moment. Therefore any experience design is about what happens on a timeline. It's all about linking multiple steps together. Brand design is more spatial. It's all at once across screens. Related
14 September
Creator of the Keras deep-learning library and the ARC-AGI benchmark.
> One could even define intelligence as the efficiency with which one converts experience into competence; by this definition they lag very far behind us Yes, one could define intelligence in this way, and one would be right. By this metric current AI is approximately 6 OOMs less intelligent than humans. Your ancestors' evolutionary history did not prepare you for Python programming, yet you can learn to competently program in Python in a few hundreds of hours. An LRM needs the training data equivalent of ~1B hours (on top of all of its non-programming related training data). Another dimensio… Quoting @DKokotajlo Dan Selsam is a current OpenAI capabilities researcher. (since 2022) He was my boss for a while. He doesn't have a twitter account but has made this public statement of his views on AI risk and sent it to me to share: Dan Selsam's Personal Statement on AI Risk: I have been working on AI for over fi… Related
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.
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
5 September
Statistician at Columbia; writes Statistical Modeling, Causal Inference, and Social Science, and wrote Bayesian Data Analysis.
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.
27 August
Independent iOS developer and podcaster; co-hosts the Accidental Tech Podcast and Analog(ue), and makes the apps Callsheet, MaskerAid and Peek-a-View.
26 August
Writer and developer. He runs the Latent Space newsletter and podcast about AI engineering, and writes essays on software and careers at swyx.io.
PSA: do not use codex "locked use" capabilities right now. it is currently relying on unstable mac features and has completely locked me out of my macos keychain twice this week. thx @_chenglou for linking to apple developer forums acknowledging this is a "known bug". just avoid. ofc, would be nice to do everything in cloud, but cloud isn't there yet. Related
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
Sociologist at Duke University writing on markets, exchange and moral order, and on plain-text and data-visualisation tools for social science.
28 July
Pseudonymous writer; posts careful, funny investigations of everyday questions — air quality, seed oils, arguing, chess — usually by reading the studies.
On a near-daily basis I get emails offering to pay for "sponsored articles" or for linking to sketchy crypto/casino sites. I guess everyone gets these? Search engines surely prohibit this, but does it get your content removed from LLM training? LLMs crypto Related
1 July
Chilean web engineer building web experiences since 2006; co-founder of Media Creators and writes at iolivares.com.
4 June
Economist at Oxford's Global Priorities Institute; works on what advanced AI would do to growth, saving and the long-run economy.
Their words
here prices are adjusting in this interesting way that too many macro models don't allow for, right? So, that what what a what's happening is what would be called investment specific technical change where yeah, the price of capital is like falling relative to the price of consumption instead of like the standard doing the standard macro thing of saying there's just output.
Show the whole quote
youtube.com
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.
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.
20 February
Indian software engineer and co-founder of Skcript; builds web apps and writes at varunraj.in.
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.
28 December 2025
Software engineer and founder of Block Party; previously an engineer at Pinterest and Quora, and a co-founder of the non-profit Project Include and the tech diversity data project Where are the Numbers?
1 December 2025
Investment researcher and engineer who runs Lyn Alden Investment Strategy, writing on macroeconomics, currency systems and equity analysis.
23 November 2025
Co-founder of Modem and a founding engineer at Sentry, where he went on to be VP of Engineering. Co-author of Third-party JavaScript, and co-host of the State of Agentic Coding podcast with Armin Ronacher.
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
31 August 2025
Indian software engineer and co-founder of Skcript; builds web apps and writes at varunraj.in.
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
31 December 2024
Programmer and teacher; writes on software, learning and the web, and makes the Coding Blocks video course.
24 July 2024
Indonesian fullstack engineer, speaker and instructor; writes about JavaScript, SvelteKit and Linux tooling at kalwabed.com.
9 May 2024
American author of The Subtle Art of Not Giving a F*ck and Everything Is F*cked. Writes essays and book reviews at markmanson.net.
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
1 June 2022
Economist; former chief economist of the International Monetary Fund.
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
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.
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.
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