Search
35 results
People
Said and published
-
bunch — Documentation repository for Bunch.app
-
doctor — Doctor - Maintain your documentation on SharePoint without pain.
-
poll: to look up the official documentation for "git pull", would you use: (you can pick more than one)
-
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.
-
r-internals — Documentation for R's internal C API
-
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…
-
An agent skill to help update your app for the iPhone Duo
-
socviz v2.0.0 — Support files for a data visualization course and book
-
Examples in documentation should be compiled and run as tests, so that changing the code breaks the docs instead of quietly outdating them.
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…
-
…about the official recommended values for ip addresses and hostnames in documentation, try to think about that as a separate…
-
If you will write a huge markdown file so an agent has context, you should have written the documentation that gives a human the same context.
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.
-
Good documentation is produced by effort, not by tooling that keeps code and docs together
This reinforced my belief that good documentation comes from effort, not tooling.
-
Anthropic prompt engineering documentation — Anthropic
I still think Anthropic have the best prompting documentation of any LLM provider.
-
Go standard library documentation — The Go authors
the Go standard library documentation is probably my favourite language reference
-
iolivares.com-v2025 — iolivares.com v2025 (AI vibecoded)
-
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…
-
Refactoring internal documentation in Notion
-
docs — Internet protocols and tools related documentation
-
Stop writing documentation for people: a library should ship markdown for agents, which then explain it to whoever asks.
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…
-
A data model for Git (and other docs updates)
-
john-000 — Look at the Nuxt 3 documentation to learn more.
-
Examples are the best documentation
-
Notion — Notion Labs
Notion for tons of stuff. Project planning. Meeting notes. Documentation. Public documents.
-
dashy — A feature-rich, modular dashboard system for ESP32 with SSD1306 OLED display. Perfect for home automation, productivity tracking, and real-time information display.
-
Just added new documentation for WSL 2 users of DotFriedRice. Now there's a mini-guide FAQ item for installing the Microsoft Terminal, WSL 2 and Arch Linux so you can install DotFriedRice in a few minutes in case you…
-
Redis patterns for coding
-
How Apollo flew to the Moon — W. David Woods
This is far and away the best general-audience technical documentation of the Apollo missions I've read.
-
Backblaze B2 Rust library
-
When two expert users argue over whether documentation is clear, that debate is unproductive — the way to actually find unclear documentation is to test it on real readers, not to have experts argue about wording.
I don’t think this is very productive (expert users of a piece of software are notoriously bad at being able to tell if an explanation will be clear to non-experts), so I needed to find a way to identify problems with…
-
AsciiDoc
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.
-
A design proposal should describe the feature as though it already existed — once as a tutorial and once as reference documentation.
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…
-
Standardised manufacturing and documentation cannot be skipped when a drug is given to human beings, because the noise they remove is the noise that would otherwise swallow the answer.
You cannot wing it when you're giving a drug to human beings.
-
A108 AUTOMATED DETECTION OF ILEOCECAL VALVE, APPENDICEAL ORIFICE, AND POLYP DURING COLONOSCOPY USING A DEEP LEARNING MODEL
-
Do not run a personal agent on a cheap or local model: weak models are gullible and easy to prompt-inject.
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…