Notes
125 entriesMisc. et al.
2026
- Three seams in a twelve-second loop
- Two deduplication windows, because the idle notice arrives late
- An undocumented ceiling, and the only paging on offer
- Six weeks looking for a signal, and what was left when there wasn't one
- Redacting network identifiers from a debug report
- The two-pointer merge that never reached the chart file
- Four sets of vendor claims, and why none of them can be ranked
- Streaming transcription, speaker labels and endpointing from open weights on a CPU
- Forking the Farcaster client: what you actually need
- Mail configuration as desired state, with a credential-free drift gate
- Measuring oracle staleness against a market that never closes
- Testing a content corpus like code, so an unsourced fact fails the build
- Selling placement instead of advice, in a directory companies claim by domain
- One page, seven files, and the two that decide whether it deploys
- Custom domains on GitHub Pages: five absolute URLs and one DNS setting
- A daily report on a systemd timer instead of a crontab line
- Manifest V3 never killed cosmetic filtering
- Keeping the model out of the verdict path
- One command that decides whether the work is done
- A Rails starter whose Stripe billing runs with zero external accounts
- Hotwire Native, and deciding which screens stop being web views
- One Stripe account, and every endpoint gets every event
- The lever on agent token cost is turns, not transport
- Assembling a reproducible exam from a bank that cannot satisfy every constraint
- Twenty lines of shell that sync a notes repo and never shout about it
- Two operating systems, one dotfiles repo, no conditionals
- Serving one documentation corpus to people and to agents
- A static site with exactly one server route
- Edge-triggered alerting for a registration window that closes in minutes
- When browser LCP measures the wrong thing on a feed
- Designing the type first and building the whole dashboard against mocks
- The two places an Astro site can put an image, and why it matters
- Four agent lifecycles, one markdown file format
- Symlinking dependencies so N worktrees do not mean N node_modules
2025
- Hand-written API docs, and the drift they cannot detect
- A trailing stop whose distance is a function of realized profit
- A weekly release digest that ran for a year
- Duplicate detection without an API
- The parts an indexer grows: a rate limiter, a verify queue, and a WAL-safe backup
- Serving a PWA manifest and service worker through the Rails view layer
- A reader with no account, and the post identity problem that creates
- Magic-link auth: the decisions the gem does not make for you
2024
- Thread-local SQLite connections, and the write lock underneath them
- Turning a week of GitHub activity into Notion blocks
- Partial success as the default outcome of a cross-post
- A frame image written as JSX, rendered on the response path
- A todo list that lives in contract storage
- Publishing a snapshot's size without hosting the snapshot
- Reading a directory from its own JSON instead of its HTML
- Where an ecosystem ends, and the headline number that moves with it
- Two block explorers, one address graph, and a result cap that truncates silently
- MTProto is not the Bot API, and the session file is a credential
- Keeping the raw payload next to the derived report
- A CI check that reads a diff and validates it against another repo
- A UNIQUE constraint as the idempotency mechanism
- One guild setting as an anti-scam control
- A Farcaster frame is meta tags and a POST handler
- Minting from a button press, and the verification that has to sit behind it
- On-chain randomness you can read before you guess
- The block number is the token id
- A contract project caught halfway between Truffle and Hardhat
2023
- What an indexer has to solve that a node does not
- Two package.json files, one repo, no workspace
- A gateway websocket and a web server in one process
- Bridging an ERC-20 to Base with cast and nothing else
- Adding a network to a token list that moves real funds
- The nonce is not the transaction count
- A faucet whose reward scales with what you hold
- "Has this person committed anything" has no correct answer
- A queue in front of a simulcast, and the double-post it invites
- Link rot in a curated list
- A security policy for a repo that runs other people's nodes
2022
2021
- A trustless FIL to WFIL bridge, and the liquidity bound at its centre
- One index.html, 730 bytes, and the floor of shipping on the web
- Talking to an Ethereum node from Ruby, where the transport options are the API
- Translating a curriculum made mostly of English links
- Aggregating a price from several APIs, and deciding what to do when they disagree
- Mounting React inside Rails, and the initial-state seam
- Three sources for one NFT listing, and why scraping is the worst
- Ethernaut level one: a fallback function is a public entry point
- Forking a Jekyll theme you intend to keep editing
2020
- Reporting three change windows without storing any history
- A JSON schema as the entire product
- Rails application templates, and the ordering problem everyone hits
- Anti-tracking blocked the signup form, so the form moved in-house
- Measuring 60+ support desks by hand, and publishing the correspondence
- Rendering MediaWiki-format proposals as a static site
- The storage number nobody warns you about when you run an explorer
- A form that posts without leaving the page, and the gate that actually enforces
- .cache committed to git, and the stale build it can cause
- Heading typography in a long-form archive
2019
2018
- Volume floors, and why percent-change rankings are noise without them
- Deriving a cross rate through a base you did not ask for
- HMAC request signing, and the clock skew that looks like an auth failure
- Percent change: the sign convention and the zero denominator
- gets.chomp.to_i returns 0, and beginners never find out
- Hundreds of emoji PNGs, and the advice HTTP/2 reversed
- Quoting a price you are willing to be held to
- A Flask app for Costa Rican market data that was never written
- normalize.css, and the dependency nobody audits
- Fetch, render and send as three modules
2017
2016
- HTTP 402 as a working payment channel
- Reselling a metered API for satoshis
- Charging for a public-good data feed
- Selling stock quotes over an endpoint Google never documented
- The same service, one string different
- Normalising free-text ingredients, and selling the ranking
- Pricing a security answer by value, not by cost
- Payment taken, extraction failed
- Selling a search whose negative result means nothing
- Account-existence oracles, sold by the request
- Bitcoin bounties for GitHub work, escrowed in 2-of-3 multisig