<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss.xsl" type="text/xsl"?><rss version="2.0"><channel><title>Teximos</title><description>A publication about technology: what just shipped, what it actually does and what it costs when it breaks.</description><link>https://teximos.com/</link><item><title>A transaction protects the write, not your closure</title><link>https://teximos.com/blog/a-transaction-protects-the-write-not-your-closure/</link><guid isPermaLink="true">https://teximos.com/blog/a-transaction-protects-the-write-not-your-closure/</guid><description>Twelve requests arrived at once against a free allowance that was already spent. None of them should have been served. Nine were, and the counter they were checked against was correct the entire time.</description><pubDate>Wed, 05 Aug 2026 12:00:00 GMT</pubDate><category>Concurrency</category></item><item><title>The stream died and the log said 200</title><link>https://teximos.com/blog/the-stream-died-and-the-log-said-200/</link><guid isPermaLink="true">https://teximos.com/blog/the-stream-died-and-the-log-said-200/</guid><description>For six sessions the complaint was that one model could not answer questions about email. Every observation behind that was true. The conclusion was wrong in every particular.</description><pubDate>Wed, 05 Aug 2026 11:00:00 GMT</pubDate><category>Streaming</category></item><item><title>A model that never worked, because a guard was keyed on spelling</title><link>https://teximos.com/blog/a-model-that-never-worked-because-a-guard-was-keyed-on-spelling/</link><guid isPermaLink="true">https://teximos.com/blog/a-model-that-never-worked-because-a-guard-was-keyed-on-spelling/</guid><description>The most expensive model in the catalogue answered every request with a 200, six hundred milliseconds and zero characters. It had done that since the day it was listed.</description><pubDate>Wed, 05 Aug 2026 10:00:00 GMT</pubDate><category>Model routing</category></item><item><title>A customer paid, and the webhook had nowhere to put it</title><link>https://teximos.com/blog/a-customer-paid-and-the-webhook-had-nowhere-to-put-it/</link><guid isPermaLink="true">https://teximos.com/blog/a-customer-paid-and-the-webhook-had-nowhere-to-put-it/</guid><description>Stripe did everything right. The subscription was active and the money had moved. The account it belonged to had no record that any of it happened.</description><pubDate>Wed, 05 Aug 2026 09:00:00 GMT</pubDate><category>Payments</category></item><item><title>A missing price billed every image at 27x</title><link>https://teximos.com/blog/a-missing-price-billed-every-image-at-27x/</link><guid isPermaLink="true">https://teximos.com/blog/a-missing-price-billed-every-image-at-27x/</guid><description>The cheapest model we served was absent from the pricing table, so it fell through to the fallback weight. Every image request in production landed on it.</description><pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate><category>Metering and billing</category></item><item><title>The baseline was priced with the wrong model</title><link>https://teximos.com/blog/the-baseline-was-priced-with-the-wrong-model/</link><guid isPermaLink="true">https://teximos.com/blog/the-baseline-was-priced-with-the-wrong-model/</guid><description>Flash was filed with Flash-Lite&apos;s rates. Nothing errored, because the number was plausible and it was the number every other price divided by.</description><pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate><category>Metering and billing</category></item></channel></rss>