Related posts
Kieran Healy
GitHub
socviz v2.0.0 — Support files for a data visualization course and book
documentation defunct datasets
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 Korrents Recommends Bluesky Site Papers
Top people
Julia Evans
Hamel Husain
Alice Ryhl
Eugene Yan
Andrej Karpathy
Daniel Stenberg
Matt Birchler
Elio Struyf
Brett Terpstra
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
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.
It's cool that there is more interest in eval tools! Some opportunities for improvement: 1. Right now, this workflow tries to quiz you up front about your recollection of your experience with a plugin. It would be better if it was more "in-situ", meaning you could give feedback on the plugins as you are using them. 2. It goes off and builds datasets and judges automatically based on what you tell it in up front as well as what's documented in the plugin. I would like to see it try to do error discovery with you first to allow you to annotate real traces / session history etc so you can figure… Quoting @ClaudeDevs New in Claude Code: claude plugin eval See what value your plugin is adding, or if it needs more work. You can create test cases, run your plugin or skill against those test cases, score those runs, then run each case again without the plugin to see the differences. 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
22 July
Climate scientist and energy systems analyst; writes The Climate Brink with Andrew Dessler and leads climate research at Stripe.
1 July
Chilean web engineer building web experiences since 2006; co-founder of Media Creators and writes at iolivares.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.
2 April
Founding member of OpenAI and former director of AI at Tesla; creator of nanoGPT and the term "vibe coding".
LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki… LLMs Related
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.
13 October 2025
Historian of invention; writes Age of Invention on where the Industrial Revolution actually came from.
1 October 2025
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.
Their words
The overall workflow is intuitive, especially for those new to formal evaluation processes. The UI guides you through creating datasets, running experiments, and annotating results.
Show the whole quote
hamel.dev
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.
17 July 2025
Creator of the Keras deep-learning library and the ARC-AGI benchmark.
Their words
However, current understanding and evaluation of world models in artificial intelligence (AI) remains narrow, often focusing on static representations learned from training on massive corpora of data, instead of the efficiency and efficacy in learning these representations through interaction and exploration within a novel environment.
Show the whole quote
arxiv.org
25 June 2025
Member of technical staff at Anthropic. He has led ML/AI teams at Amazon, Alibaba and Lazada, and writes about LLMs, recommender systems and engineering at eugeneyan.com.
Wrote an intro to evals for long-context Q&A systems: • How it differs from basic Q&A • What dimensions & metrics to eval on • How to build llm-evaluators • How to build eval datasets • Benchmarks: narratives, technical docs, multi-docs eugeneyan.com
LLMs benchmarks Related
22 June 2025
Member of technical staff at Anthropic. He has led ML/AI teams at Amazon, Alibaba and Lazada, and writes about LLMs, recommender systems and engineering at eugeneyan.com.
benchmarks
Their words
Since these datasets are likely already part of model training data, we shouldn't rely solely on them to evaluate our Q&A system.
Show the whole quote
eugeneyan.com
Member of technical staff at Anthropic. He has led ML/AI teams at Amazon, Alibaba and Lazada, and writes about LLMs, recommender systems and engineering at eugeneyan.com.
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
27 September 2024
Software engineer, Wikipedia editor and crypto critic; writes Citation Needed and runs Web3 is Going Just Great.
energy
Their words
Each shift takes its toll, and everyone has a limit of how much energy they’re willing to expend on a new platform that will eventually, like its predecessors, join the graveyard of defunct websites.
Show the whole quote
citationneeded.news
24 July 2024
Indonesian fullstack engineer, speaker and instructor; writes about JavaScript, SvelteKit and Linux tooling at kalwabed.com.
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
10 February 2022
Co-founded Neuralink and founded Science Corp, which is building a retinal implant; writes about neural interfaces and biology.
Mindstate Design Labs In the paper Psychedelics and the Human Receptorome by Thomas Ray there is a supplementary material table that is one of my favorite datasets of all time. I keep a copy of it on my laptop, with some extra color-coding,…
psychedelics Related
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