Software Engineer
Writing
Notes from building things. Mostly about picking one constraint and following where it leads.
- The last four pointsNewA perfect Lighthouse score taught me very little about making the page fast, and a great deal about how fast is measured.
- Three stacksWhat I actually use, and why the honest answer is three different answers. Each one is downstream of a single constraint I refused to give up.
- Everything in the binary, about HaypileOne rule, no network calls, and the code it forced. A transformer reimplemented in Go, quantized to fit, and proved correct against the original.
- Everything except the bytes, about LensdropUploading forty gigabytes is not a bandwidth problem. It is a coordination problem, and the coordination is where all the bugs live.
- Where the key lives, about KlefEncrypting a secret is the easy part. The harder question is what happens to the decrypted key afterwards, and how long you let it exist.