technical writing
What is written here was built first.
Longer pieces about the work: what I built, why it is built that way, and what went wrong on the way there. Each one is about something public, and every project it mentions has a page of its own in the register of holdings.
Most software you use today runs on someone else’s computer. Local-first software runs on yours. Here is what that changes, what it costs, and why nearly everything I build works this way.
2026-08-28 · 5 min read · on Stack-Sight, bruhswer, Digital Footprint CleanerThe Pulse Engine reads prices and news and prints one number. The number was the easy part. Making it say how it got there took far longer, and that is the part that makes it worth anything.
2026-08-28 · 5 min read · on The Pulse EngineI built a transformer from nothing, starting at the character tokenizer and working up through BPE and RoPE. Not to produce anything useful, but to find out whether I understood the internals or only the diagrams.
2026-08-28 · 4 min readAlmost every neural network is trained by backpropagation. There is another way: let the network mutate its own structure and keep whatever works. Quantum Neural Horror does that, and lets you watch it happen.
2026-08-28 · 4 min read · on Quantum Neural HorrorBruhswer is a hardened browser for Windows. The most useful thing in it is not a protection. It is the words NOT ENFORCEABLE, printed whenever it cannot actually do what it claims.
2026-08-28 · 4 min read · on bruhswer, Image-ProtectorMost advice about writing good code arrives as a rule you are told to follow. This is the opposite: write the terrible version on purpose, measure exactly what it costs, and let the rule be the conclusion instead of the premise.
2026-08-28 · 4 min read · on coding-war-crimes, NCAA Outcome Predictor