Featured
A layered CLAUDE.md, tight permissions, hooks, skills and scoped MCP servers: the setup that keeps Claude Code safe and cheap across dozens of repositories.
13 min
Senior Software Engineer & Cloud Architect · Italy
I design, harden and cut the cost of production systems on Google Cloud.
This is where I write, in long form, about the systems I build and run: cloud architecture on Google Cloud, backend design, security, and using AI tools without lowering the bar. Each piece is a decision I had to make, with the trade-offs and the numbers behind it.
Featured
A layered CLAUDE.md, tight permissions, hooks, skills and scoped MCP servers: the setup that keeps Claude Code safe and cheap across dozens of repositories.
13 min
A practical split for small teams: coarse per-client limits at the edge, per-user and per-cost limits in the service, and the 429 behaviour both must share.
11 min
How a small team can keep Terraform state safe: a versioned GCS backend, locking you can trust, and a state layout that limits the damage of a bad apply.
10 min
Which Postgres schema changes lock a table, which are safe, and the three-release pattern I use to change a live column without an outage or a long window.
12 min
Most small teams should not start with a service perimeter. The organization prerequisite, the friction it adds, and when it pays for itself.
9 min
Thirty well-chosen cases, deterministic checks first and a model judge last, run several times per case. A practical eval setup a single developer can maintain.
11 min
Most incident reviews end as documents nobody opens again. A one-page format, actions filed as ordinary issues and a thirty-day check make change likely.
9 min
I’m a senior software engineer and cloud architect based in Italy. I work on backend systems and the platforms under them, mostly on Google Cloud, and I care about the parts that decide whether a system is still cheap and calm a year after launch.
More about me →Cost is a feature.
Spend is a design input, reviewed alongside latency and error rates.
Boring infrastructure, interesting product.
Plain, managed building blocks, so the novelty goes where users can see it.
Measure before you optimise.
No change ships without a number before and a number after.
Work with me · Availability on request