lee.yt

Before a GPS satellite is launched, its atomic clock is set to the wrong frequency. On purpose. The clock is supposed to tick at 10.23 million times a second. Engineers set it to 10.22999999543 million. That’s slower by about 4.5 parts in ten billion. Without that change, the clock would gain about 39 microseconds a day on a ground clock, enough for light to travel more than 11 kilometers. Here’s why. ...

Why is the speed limit of the universe tied to light and not to gravity or something else? Does light really travel at that limit? And what if the photon turned out to have a tiny mass? These questions intrigue me, and they turn out to share one answer. It starts with an idea: c isn’t really about light. It’s the speed limit on cause and effect, the fastest anything can travel from one event to another and still change what happens there. Light just happens to be able to reach it. I’ll build up to that from something software engineers already know. ...

I finally wrote the material I kept telling people I’d get around to. Omnist now has a proper introduction deck and a hands-on tutorial. The deck is language-agnostic — it explains the spec itself, not any one port’s API. The tutorial uses Python to walk through every model and feature with real, working code. Why a deck and a tutorial, not just docs The specification is precise on purpose. Precise documents are a bad place to start. You shouldn’t have to read a spec before you know if something is worth your time. The deck is the fifteen-minute version: what problem Omnist solves, and why the model looks the way it does. The tutorial is for someone who’s already decided to try it. Every example is real, working code, checked and run before it went in the page. It’s built as steps, so you can do them out of order once you know your way around. ...

A library gets proven by people using it. A specification is a harder claim to back up: someone else has to build from your rules alone, without being able to ask you what you meant. I wanted Omnist to become a real document and schema standard, not just a library that happened to do well. So I planned for that early on: get the design out of one language, and check that it actually holds up in several others, before I called any of it a standard. ...

Two posts ago, R and D were two roles, two rulebooks, one person switching hats. Last time was D’s story: the loop that made shipping safe. By now the two don’t split cleanly — every decision and every build happen in the same conversation. This round adds a third: QA, an external auditor with no stake in the code already being good, brought in specifically to check R and D’s work from the outside. ...