Brandur Leach
Software engineer at River, previously at Stripe, Heroku and Snowflake; writes about APIs, infrastructure and software design at brandur.org.
Brandur Leach did not write this page. ppll compiled it from their own words, each linked to the source. Is this you? · Report a mistake
Latest GitHub
What they believe
-
Even with LLMs, building software yourself still costs real ongoing human time, so replacing a paid tool with an LLM-built internal one often does not pay off.
While LLMs have made software considerably cheaper to build, they haven't brought it to zero. Good LLM-built systems still involve a feedback loop, where an operator has the model work for a while, makes adjustments based on results, asks for another pass, refines further, and so on
brandur.orgSaid 31 May 2026This on korrents
-
As people use agents more, having an API should become a competitive edge that sets a service apart from its competitors.
As this mode of operation gets more popular, expect the availability of an API to be a competitive edge that differentiates a service from its competitors.
brandur.orgSaid 27 Mar 2026This on korrents
The bold line is korrents’ wording; the quote is theirs. These 2: what they wrote before what they said aloud, one per source, newest first.
Feed
As its own page →Hiding
2 November
17 September
7 September
10 July
19 June
31 May
From one piece The Minimum Viable Unit of Saleable Software 2 beliefs · brandur.org
-
Their words
I'm contending (and/or hoping) that for a software package of arbitrary complexity, there's a zone of viability in which when priced within reason, it'll make sense to buy over build, even given the existence of the powerful LLMs that've become our daily companions
-
Their words
While LLMs have made software considerably cheaper to build, they haven't brought it to zero. Good LLM-built systems still involve a feedback loop, where an operator has the model work for a while, makes adjustments based on results, asks for another pass, refines further, and so on
27 March
From one piece The Second Wave of the API-first Economy 2 beliefs · brandur.org
-
korrents.com
The convention of the future will be human language typed into something like a terminal and fulfilled via API.Their words
The convention of the future will be human language, fed into what looks a lot like a terminal, and fulfilled via API.
-
Their words
As this mode of operation gets more popular, expect the availability of an API to be a competitive edge that differentiates a service from its competitors.
24 September 2025
1 September 2025
17 July 2025
4 April 2025
12 December 2024
13 November 2024
25 June 2024
28 May 2024
From one piece Eradicating N+1s: The Two-phase Data Load and Render Pattern in Go 2 beliefs · brandur.org
-
korrents.com
Go is no less susceptible to N+1 queries than a metaprogramming-heavy language like Ruby, despite its verbosity.Their words
Despite Go's ad nauseum verbosity, it's no less susceptible to N+1s than a language heavy in metaprogramming like Ruby.
-
korrents.com
N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.Their words
This practically invisible problem is probably number two to only forgotten indexes as the most common reason for poor performance of web apps around.
20 May 2024
6 May 2024
From one piece The Notifier Pattern for Applications That Use Postgres 2 beliefs · brandur.org
-
korrents.com
Postgres listen/notify is an incredible feature that is useful in all kinds of situations.Their words
Listen/notify in Postgres is an incredible feature that makes itself useful in all kinds of situations.
-
korrents.com
Postgres connections are still somewhat of a precious, limited resource that should be conserved.Their words
Despite optimizations over the years, connections in Postgres are still somewhat of a precious, limited resource, and should be conserved.
5 May 2024
From one piece Web APIs: Enriched DX By Disallowing Unknown Fields 2 beliefs · brandur.org
-
korrents.com
Webhook receiving endpoints are a common place where unknown fields in the payload should not be rejected.Their words
A common place where DisallowUnknownFields should not be applied are webhook receive endpoints.
-
Their words
It's a feature that's not needed every day, but it's easy to implement, and the day it is, it'll save hours worth of time and frustration.
20 November 2023
From one piece River: a Fast, Robust Job Queue for Go + Postgres 2 beliefs · brandur.org
-
korrents.com
A software stack with a single dependency, Postgres, is easier to operate than one with many components.Their words
dependency minimization is great. I've written previously about how at work we run a single dependency stack. No ElastiCache, no Redis, no bespoke queueing components, just Postgres. If there's a problem with Postgres, we can fix it.
-
Their words
transactions are really just a really good idea. Maybe the best idea in robust service design.
26 August 2023
From one piece On Using Go's `t.Parallel()` 2 beliefs · brandur.org
-
korrents.com
Leaking goroutines without realizing it is easily one of Go's top footguns, so tests should check for leaks.Their words
Our tests use goleak to detect any accidentally leaked goroutines, a practice that I'd recommend since leaking goroutines without realizing it is easily one of Go's top footguns.
-
Their words
As some packages grow to be large, parallel testing will keep them fast, and annotating tests with t.Parallel() from the beginning is a lot easier than going back to add it to every test case and fix parallelism problems later on.
19 July 2022
-
korrents.com
Soft deletion is rarely used to actually undelete data, because deletion has side effects that a flag cannot reverse.Their words
As far as I'm aware, never once, in ten plus years, did anyone at any of these places ever actually use soft deletion to undelete something.
10 September 2021
8 September 2021
16 February 2021
1 December 2020
7 August 2019
4 June 2019
28 May 2019
Nothing matches.
Beliefs
Korrents What they believe 16 beliefs — each backed by an exact quote.
Each is a — compiled by korrents.com, not by them: the one-line wordings are korrents', the quotes are theirs.
Recent
Even with LLMs, building software yourself still costs real ongoing human time, so replacing a paid tool with an LLM-built internal one often does not pay off.
While LLMs have made software considerably cheaper to build, they haven't brought it to zero. Good LLM-built systems still involve a feedback loop, where an operator has the model work for a while, makes adjustments based on results, asks for another pass, refines further, and so on
The Minimum Viable Unit of Saleable Software Said 31 May 2026
Software that is novel enough to be non-trivial to rebuild with an LLM, and priced within reason, will still be worth buying rather than building.
I'm contending (and/or hoping) that for a software package of arbitrary complexity, there's a zone of viability in which when priced within reason, it'll make sense to buy over build, even given the existence of the powerful LLMs that've become our daily companions
The Minimum Viable Unit of Saleable Software Said 31 May 2026
As people use agents more, having an API should become a competitive edge that sets a service apart from its competitors.
As this mode of operation gets more popular, expect the availability of an API to be a competitive edge that differentiates a service from its competitors.
The Second Wave of the API-first Economy Said 27 Mar 2026
Show 13 more
The convention of the future will be human language typed into something like a terminal and fulfilled via API.
The convention of the future will be human language, fed into what looks a lot like a terminal, and fulfilled via API.
The Second Wave of the API-first Economy Said 27 Mar 2026
N+1 queries are probably the second most common cause of poor web app performance, after forgotten indexes.
This practically invisible problem is probably number two to only forgotten indexes as the most common reason for poor performance of web apps around.
Eradicating N+1s: The Two-phase Data Load and Render Pattern in Go Said 28 May 2024
Go is no less susceptible to N+1 queries than a metaprogramming-heavy language like Ruby, despite its verbosity.
Despite Go's ad nauseum verbosity, it's no less susceptible to N+1s than a language heavy in metaprogramming like Ruby.
Eradicating N+1s: The Two-phase Data Load and Render Pattern in Go Said 28 May 2024
Postgres connections are still somewhat of a precious, limited resource that should be conserved.
Despite optimizations over the years, connections in Postgres are still somewhat of a precious, limited resource, and should be conserved.
The Notifier Pattern for Applications That Use Postgres Said 6 May 2024
Postgres listen/notify is an incredible feature that is useful in all kinds of situations.
Listen/notify in Postgres is an incredible feature that makes itself useful in all kinds of situations.
The Notifier Pattern for Applications That Use Postgres Said 6 May 2024
Rejecting unknown fields in API requests is easy to implement and, on the day it is needed, saves hours of time and frustration.
It's a feature that's not needed every day, but it's easy to implement, and the day it is, it'll save hours worth of time and frustration.
Web APIs: Enriched DX By Disallowing Unknown Fields Said 5 May 2024
Webhook receiving endpoints are a common place where unknown fields in the payload should not be rejected.
A common place where DisallowUnknownFields should not be applied are webhook receive endpoints.
Web APIs: Enriched DX By Disallowing Unknown Fields Said 5 May 2024
Transactions are the best idea in robust service design.
transactions are really just a really good idea. Maybe the best idea in robust service design.
River: a Fast, Robust Job Queue for Go + Postgres Said 20 Nov 2023
A software stack with a single dependency, Postgres, is easier to operate than one with many components.
dependency minimization is great. I've written previously about how at work we run a single dependency stack. No ElastiCache, no Redis, no bespoke queueing components, just Postgres. If there's a problem with Postgres, we can fix it.
River: a Fast, Robust Job Queue for Go + Postgres Said 20 Nov 2023
Annotating Go tests with t.Parallel() from the start is much easier than adding it later and fixing the parallelism problems that surface.
As some packages grow to be large, parallel testing will keep them fast, and annotating tests with t.Parallel() from the beginning is a lot easier than going back to add it to every test case and fix parallelism problems later on.
On Using Go's `t.Parallel()` Said 26 Aug 2023
Leaking goroutines without realizing it is easily one of Go's top footguns, so tests should check for leaks.
Our tests use goleak to detect any accidentally leaked goroutines, a practice that I'd recommend since leaking goroutines without realizing it is easily one of Go's top footguns.
On Using Go's `t.Parallel()` Said 26 Aug 2023
Soft deletion is rarely used to actually undelete data, because deletion has side effects that a flag cannot reverse.
As far as I'm aware, never once, in ten plus years, did anyone at any of these places ever actually use soft deletion to undelete something.
Soft Deletion Probably Isn't Worth It Said 19 Jul 2022
Soft deletion makes a database worse by bleeding deletion logic into every query and rendering foreign keys mostly useless.
The first is that soft deletion logic bleeds out into all parts of your code.
Soft Deletion Probably Isn't Worth It Said 19 Jul 2022
What is a korrent?
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.
Where they publish
Site brandur.org Essays on APIs, infrastructure and software design.
Recent
- The Minimum Viable Unit of Saleable Software 31 May 2026 LLMs made software cheaper to build, but not free. A look at the new buy-vs-build math of the LLM age, and the pricing zone where small software businesses can still survive.
- The Second Wave of the API-first Economy 27 Mar 2026 APIs were meant to make the web programmable and interoperable. A combination of revenue chasing, security concern, and abuse reversed the trend for a decade as walls went up instead of down. Today, LLMs are changing th…
- Eradicating N+1s: The Two-phase Data Load and Render Pattern in Go 28 May 2024 Using a two-phase data load and render pattern to prevent N+1 queries in a generalized way. Especially useful in Go, but applicable in any language.
Show 17 more
- The Notifier Pattern for Applications That Use Postgres 6 May 2024 Maximizing Postgres connection economy by using a single connection per program to receive and distribute all listen/notify notifications.
- Web APIs: Enriched DX By Disallowing Unknown Fields 5 May 2024 Using Go’s DisallowUnknownFields option to improve an API’s integration experience by making paramter naming mistakes faster to resolve.
- River: a Fast, Robust Job Queue for Go + Postgres 20 Nov 2023 Introducing River, a Postgres-based job queue designed for resilience and correctness through strong transactional guarantees.
- On Using Go's `t.Parallel()` 26 Aug 2023 How and why we started annotating all our Go tests with t.Parallel(), and why you might want to consider doing so too.
- Soft Deletion Probably Isn't Worth It 19 Jul 2022 The traditional soft deletion pattern using deleted_at columns leaks into code, curbs the usefulness of foreign keys, and makes data removal difficult. Luckily, there’s an alternative.
- Postgres: Boundless `text` and Back Again 10 Sept 2021 The text type in Postgres, why it’s awesome, and why you might want to use varchar anyway. Also, a story about trying to get string parameters bounded at Stripe.
- How We Went All In on sqlc/pgx for Postgres + Go 8 Sept 2021 Touring the ORM and Postgres landscape in Go, and why sqlc is today’s top pick.
- Minimally Invasive (and More Accurate) Analytics: GoAccess and Athena/SQL 16 Feb 2021 A privacy and GDPR-friendly approach to producing basic and complex site analytics, and one which is more accurate in an age when adblockers reign supreme.
- Feature Casualties of Large Databases 1 Dec 2020 Databases shed important RDMS features as they get big. Examining why this tends to be the case, and some ideas for preventing it.
- Doubling the Sorting Speed of Postgres Network Types with Abbreviated Keys 7 Aug 2019 Making the sorting speed of network types in Postgres twice as fast by designing SortSupport abbreviated keys compatible with their existing sort semantics.
- Sequences: A Modest, Contra-garden Travel Project 4 Jun 2019 In the spirit of the continued production of independent content, I’m running a two-week photography and writing project in Berlin called Sequences.
- Building a Robust Live Reloader with WebSockets and Go 28 May 2019 A walkthrough of the design of a live reload feature for the static site generator that builds this site, touching on fsnotify, WebSockets, and the curious case of file 4913.
- SortSupport: Sorting in Postgres at Speed 4 Feb 2019 How Postgres makes sorting really fast by comparing small, memory-friendly abbreviated keys as proxies for arbitrarily large values on the heap.
- How to Manage Connections Efficiently in Postgres, or Any Database 15 Oct 2018 Hitting the limit for maximum allowed connections is a common operational problem in Postgres. Here we look at a few techniques for managing connections and making efficient use of those that are available.
- A Missing Link in Postgres 11: Fast Column Creation with Defaults 28 Aug 2018 How a seemingly minor enhancement in Postgres 11 fills one of the system’s biggest operational holes.
- Tweeting for 10,000 Years: An Experiment in Autonomous Software 20 Jul 2018 Using the design principles of a 10,000 year clock to build a program that’s intended to run on a macro timescale.
- Living APIs, and the Case for GraphQL 8 Jun 2018 Why it makes sense to model APIs as graphs, and what GraphQL can do for us to help with discovery, batch operations, and gradual enhancement.
Link verified 25 Sept 2026. Recent items update automatically from the channel.
GitHub brandur sorg (the site's own source) and other projects.
Recent
- blimpyb — Archived blog of Blimpyb, converted to Markdown. 2 Nov 2026
- sorg — A Go-based static site generator that compiles brandur.org. 17 Sept 2026
- brandur 17 Sept 2026
Show 14 more
- redis-cell — A Redis module that provides rate limiting in Redis as a single command. 7 Sept 2026
- passages-signup — A backend for the signup forms of my newsletters "Nanoglyph" and "Passages & Glass". 10 Jul 2026
- hncheck-runner 19 Jun 2026
- hncheck — A very simple app that checks to see if something under one of your domains has been submitted to HN, and emails you if it has. 19 Jun 2026
- csrf 24 Sept 2025
- cping 1 Sept 2025
- logfmt — logfmt parser in Rust. 17 Jul 2025
- modulir — Modulir is an experimental mini-framework for static site generation. 4 Apr 2025
- imagemagick-builder 12 Dec 2024
- test-2024-repo 13 Nov 2024
- go-mod-test-public 25 Jun 2024
- simplebox — Package simplebox provides a simple, easy-to-use cryptographic API where all of the hard decisions have been made for you in advance. 20 May 2024
- qself-brandur 10 Apr 2024
- sinatra-router — A tiny vendorable router that makes it easy to try routes from a number of different modular Sinatra applications. 27 Jan 2024
Link verified 25 Sept 2026. Recent items update automatically from the channel.
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.