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.
Technical & business perspectives
What we're learning building custom websites and software.
We started auditing accessibility on client projects and didn't like what we found
We ran eight client projects through a basic accessibility pass and almost all of them failed: contrast, focus traps, a checkout that relied on hover. Including our own code.
We audited our own server's security and found things we'd never let a client get away with
We went over sinadoapps.com's deployment with the same standard we hold clients to, and it didn't come out well: unverified SSH keys, missing headers, an unrestricted API key.
Adding Galician to our own site: what we learned doing i18n without libraries
How we added Spanish, English and Galician to sinadoapps.com without an i18n library, and the dumb mistake that made a whole post disappear from the site's routes.
Quoting a website project: why the first number is almost never the right one
How we quote projects at the agency, what blew our margin on a real job, and what we changed afterwards.
Backups: what we learned the day a host went down without warning
A client lost three weeks of content to a disk failure on cheap hosting. Since then we test every backup before calling a project finished.
The AI tools we actually use day to day (and the ones we dropped)
Skills, MCPs and subagents: how we built our AI workflow at the agency, including the stuff we tried that didn't work out.
What we found inheriting a WordPress abandoned by another agency
No credentials, dead plugins and a config file exposed in plain text: this is what it was like taking over maintenance of a store another agency walked away from.