What game engines taught us about AI interfaces
A game has to respond in sixteen milliseconds or it feels broken. Most AI tools have no equivalent standard, and you can feel it.
Practical writing on telephony, healthcare, AI and game development — what we built, what worked, and why.
A game has to respond in sixteen milliseconds or it feels broken. Most AI tools have no equivalent standard, and you can feel it.
Nobody gets excited about phone calls anymore. That's exactly why the numbers are still so good for the people paying attention.
Our first bidding design asked every buyer in turn. It was simple, correct, and far too slow. Here's what replaced it.
The fix for AI-generated projects nobody can maintain wasn't a better model. It was giving the generator fewer choices.
Building where a mistake reaches a patient changes how you write software elsewhere too. Some of those habits are worth keeping even when nobody's auditing you.
Carriers go down, packets drop, calls disconnect mid-sentence. Telephony forces you to design for the failure case first — most software would be better if it did.
We'll email you when there's a new article. Usually once or twice a month, sometimes less. Unsubscribe whenever.