Why You Still Can't See the Changes We Already Published on Your Site
Why you can't see the changes on your site right after we publish them: browser cache, server cache, and how we set both up in nginx.
Our blog
Technical & business perspectives
What we're learning building custom websites and software.
Why we still pay for our own VPS instead of jumping on the serverless wave
A client asked why we don't just deploy on Vercel like everyone else. The real reason has more to do with a nasty billing scare than with saving money.
The day a minor dependency patch took down a client's checkout
Why we stopped auto-updating dependencies after a real production incident took down a client's checkout, and the rule we use now.
Why it took us three years to start writing automated tests (and what changed our minds)
The story of a double-booking bug that convinced us to start testing, and the rule I use now to decide where it's actually worth it.
How we find out something broke in production before the client does
The time a checkout had been broken since Friday night and the client told us on Saturday. How we set up real monitoring after that.
We started auditing accessibility on client projects and didn't like what we found
We ran a basic accessibility check on eight client projects and nearly all of them failed: contrast, focus traps, a checkout that relied on hover.
We audited our own server's security and found things we'd never let a client get away with
We audited our own server the way we audit our clients': unverified SSH keys, missing security headers, an unrestricted API key.
Adding Galician to our own site: what we learned doing i18n without libraries
How we added Galician to our site without an i18n library, and the dumb mistake that made a whole post disappear from the site's routes.