This is where I put in writing the things that wouldn’t quite fit elsewhere. Not a corporate blog, not a newsletter, not a product. Just a personal editorial space, updated when I have something to say — usually when an idea has stopped shape-shifting for a couple of days.
I write because putting a thought in plain prose is the only way I know to find out whether I actually think it. Most of what ends up here starts as a conversation, a margin note, a voice memo at eight in the evening. Then it settles, dries, and if it still stands it becomes an essay.
Recurring themes
- AI and society. Not the “isn’t it amazing” angle, but AI as a political fact: who builds it, who controls it, who pays for the externalities.
- European digital sovereignty. Not as a slogan. As an architectural question: cloud, stack, dependencies, who keeps their hand on the kill-switch.
- Compliance as architecture. CRA, AI Act, PLD, NIS2, EAA. I’m convinced that European software between 2026 and 2027 won’t “check” compliance at the end of a project: it has to be designed in from day one.
- The craft of software. Things I’ve stopped doing, things I’ve learned to delegate, things I only got right after fifteen years.
- Advisory and IT services. The structural blind spot of traditional sourcing advisory, the end of time & materials, what a vendor knows that an analyst never will.
- Applied tech culture. Sometimes a supermarket parking lot at 18:30 tells you more than a white paper.
Voice
I write directly, without jargon when jargon isn’t needed, with jargon when it is. I don’t use bullet lists to pad a sentence, and I don’t use emoji. When I don’t know something, I say so. When I’m wrong, I go back to the essay — posts carry, when relevant, a last revised date.
I write in Italian because I work in Italy and because technical Italian deserves more room than it usually gets. I translate into English what makes sense to translate — some things stay in Italian on purpose.
Who I write for
For people who ship software for clients that aren’t only startups. For technical leaders in companies that have to produce, not pitch. For the ones who handle compliance and don’t want to call it “ticking boxes”. For anyone who still thinks the quality of the reasoning matters more than the speed of the output.
How it’s built
Plain static site, written in Markdown, kept in Git. No third-party
trackers, no ad-tech cookies, no intrusive analytics. There’s a
/llms.txt and a /llms-full.txt for
anyone indexing the site with an LLM, so they don’t have to
reverse-engineer the DOM.
Credits
Editorial palette and rhythm inspired by The New York Times Magazine, Dense Discovery and Robin Sloan’s notes.