I write about the details that remove friction before it finds you.
Bio
I'm Valerio — a software architect with twenty years across the full breadth of the stack. Backend in Java and Python, frontend in modern SPAs, cloud on AWS, and persistence across whatever the problem required: relational, document, columnar. vmcforge is the notebook I keep so the hard-won parts don't disappear into old Slack threads.
The work I've actually done: complex product design from concept to production, enterprise architecture, fintech infrastructure, regulatory compliance platforms, AI services. I've made the same mistakes at enough different companies to recognise where they come from. Most of them live in the gap between what the system does today and what the business will need it to do in eighteen months.
I write because twenty years of cross-stack, cross-domain experience is only useful if it's transferable. These essays are an attempt at that transfer.
Trajectory
- 2024 — now Software Architect · AI & product platforms
AI-as-a-service infrastructure, billing systems
ML platform design, production inference pipelines, greenfield product architecture.
- 2012 — 2024 Principal Architect · fintech & compliance
Regulatory platforms, financial data pipelines
Solvency II, Basel III, IFRS. The kind of correctness requirements that make you think twice about every schema change.
- 2008 — 2012 Senior Engineer · enterprise software
JEE architecture, ESB integration, first cloud migrations
Large-scale Java systems, service buses, the moment I realised distributed systems are just failure with extra steps.
- 2006 — 2008 Backend Engineer · early career
APIs, databases, and learning things the hard way
Where the opinions come from.
The stack
What this site is built with, and what I tend to reach for at work. None of it is novel. All of it is paid for.
Get in touch
I read everything. I reply to most things. The best way to start a conversation is with a specific question.