skip to content

day 277 of the operation / 05.10.2026

Proxfrito

the part of the site you can send to your boss

Technical.

Reviewed technical writing, with code that runs and opinions that hold up. If you ended up here at some point because of a meme, welcome — that was exactly the plan.

  1. 01
    11 min read2026-10-04

    The container isn't slow. The shared folder is.

    On Windows there are two routes to having Docker — the Desktop with the WSL2 backend, or the Engine inside the distro itself — and both trip over the same spot: where the files live. I measured both sides, brought up the stack, and ran the agent inside the container.

    • docker
    • wsl
    • linux
    • infra
    • ai
  2. 02
    1 min read2026-10-04

    A withdrawal with no response isn't a failed withdrawal

    On Solana, UTXO is the model of the Cloak notes we use — not the network's native model. A missing response doesn't prove failure either.

    • solana
    • privacy
    • security
  3. 03
    3 min read2026-10-03

    The hash checks out. The chain hasn't seen it yet

    SHA-256 passed in the browser; the stamp on Solana stopped before the send. Separating the two things is part of the experiment.

    • sha-256
    • solana
    • devnet
    • security
  4. 04
    5 min read2026-10-01

    The cheapest decision that resolves it

    Not every request needs the expensive model. Much of routing fits in a regular expression — and the real problem is finding out which, with a suite and a meter, not intuition.

    • architecture
    • ai
    • performance
    • testing
  5. 05
    5 min read2026-09-28

    Your index exists and the planner ignores it: five reasons

    Postgres almost never 'chooses the wrong path'. It chooses the right path for the cost it thinks exists — and you've spent the last few months lying to it.

    • postgres
    • database
    • performance
    • indexes
  6. 06
    4 min read2026-09-22

    Where to put the rule: client, server, or database

    Every architecture discussion starts with the wrong question. The right question is: through how many paths can this data be written?

    • architecture
    • validation
    • database
    • backend
  7. 07
    4 min read2026-09-14

    Three questions before putting cache on anything

    Cache isn't optimization, it's a contract of tolerance for stale data. If you can't write that contract, you don't know what you're putting into production.

    • cache
    • performance
    • backend
    • redis