This is an anchor-linked version of the excellent, amazing original opus magnum by Michael Tandy.
Counterexample: Royal Opera House, Covent Garden, London, WC2E 9DD, United Kingdom.
Counterexample: 1A Egmont Road, Middlesbrough, TS4 2HT
| # ============================================ | |
| # Ghostty Terminal - Complete Configuration | |
| # ============================================ | |
| # File: ~/.config/ghostty/config | |
| # Reload: Cmd+Shift+, (macOS) | |
| # View options: ghostty +show-config --default --docs | |
| # --- Typography --- | |
| font-family = JetBrainsMonoNerdFont | |
| font-size = 14 |
This is an anchor-linked version of the excellent, amazing original opus magnum by Michael Tandy.
Counterexample: Royal Opera House, Covent Garden, London, WC2E 9DD, United Kingdom.
Counterexample: 1A Egmont Road, Middlesbrough, TS4 2HT
By Patrick McKenzie (patio11) (original location: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/)
John Graham-Cumming wrote an article today complaining about how a computer system he was working with described his last name as having invalid characters. It of course does not, because anything someone tells you is their name is — by definition — an appropriate identifier for them. John was understandably vexed about this situation, and he has every right to be, because names are central to our identities, virtually by definition.
I have lived in Japan for several years, programming in a professional capacity, and I have broken many systems by the simple expedient of being introduced into them. (Most people call me Patrick McKenzie, but I’ll acknowledge as correct any of six different “full” names, any many systems I deal with will accept precisely none of them.) Similarly, I’ve worked with Big Freaki
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| name | true-name |
|---|---|
| description | Name things well. Use when the user wants a name, rename, name critique, candidate list, or true-name search for a product, company, project, package, feature, system, tool, or library. |
A discipline for naming things well.
Do not start with candidates. First find the shape of the thing: what it is, who it is for, what world it implies, and what constraints it must survive.
| # It's annoying to grab the mouse just to click the paste button | |
| # .config/i3/config | |
| # Paste | |
| # Mac users may have to use click 3 | |
| bindsym XF86Launch3 exec xdotool click 2 |
| Filter | Description | Example |
|---|---|---|
| allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
| intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
| inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
| allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
| intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |