<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Frameharbor</title><link>https://cdn-307e85.md.frameharbor.net/</link><description>Frameharbor</description><item><title>Small team, boring tools</title><description>Why most of our stack is older than our youngest engineer.</description></item><item><title>Our approach to capacity planning</title><description>We plan for the launch day, not the average day. That changes the maths.</description></item><item><title>Why we stopped compressing everything</title><description>Some payloads got bigger, some CPUs got hotter. A short tour of the trade-offs.</description></item><item><title>Range requests are harder than they look</title><description>Partial content, caching keys and the clients that ignore both.</description></item><item><title>Notes from migrating our storage tier</title><description>We moved four petabytes without a maintenance window. Here is what went wrong along the way.</description></item><item><title>Choosing points of presence on a budget</title><description>Latency maps, transit prices and the one spreadsheet that decided it.</description></item></channel></rss>
