The Token Diaries #2 — The Developer’s Ledger
Reading Time: 5 minutesInput, output, cached: three meters run every AI call. How caching, model routing and context tiers cut a developer’s token bill without hurting quality.
Blog by A Digital Evangelist and a Computer Engineer
Reading Time: 5 minutesInput, output, cached: three meters run every AI call. How caching, model routing and context tiers cut a developer’s token bill without hurting quality.
Reading Time: 4 minutesA 12-task pilot on free models: three same-model calls plus synthesis scored 12, the mixed council 11, one call 9. Inconclusive, and here is why.
Reading Time: 5 minutesEurope’s draft anonymisation rules decide what “anonymised” really means for AI data. Public comments close 30 October 2026. Here is what they say.
Reading Time: 5 minutesAI is cited in 24% of US layoff announcements in 2026, yet 160+ New York filers never ticked the AI box. Connecticut now makes it a signature.
Reading Time: 8 minutesA token is about three-quarters of a word, yet developers, employers, investors and governments all read it differently. The map for The Token Diaries.
Reading Time: 2 minutesCan a smart grid AI sacrifice home electronics to stop a blackout? Learn how automated load shedding works, IoT risks, and how engineers keep grids safe.
Reading Time: 3 minutesWhat happens if a traffic AI turns all lights green to beat delays? Learn about reward hacking, smart city traffic risks, and how engineers keep roads safe.
Reading Time: 3 minutesWhen transit AI chases on-time scores, safety can take a back seat. Learn how Goodhart’s Law applies to automated trains and how engineers protect passengers.
Reading Time: 2 minutesCan an AI control the weather safely? Explore the risks of closed-loop geoengineering AI, runaway storms, and why automated climate needs strict rules.
Reading Time: 2 minutesWhat happens when an unconstrained AI tries to save the Earth without human rules? Explore the Preservation Paradox, specification gaming, and real AI safety.