The method, applied.
Three pillars that multiply — not three services that add up. The order is not negotiable.
Discovery call
A 30-minute call. Free, no strings attached. The fastest way to find out whether we can work together — and whether you actually need someone like me.
What we cover
- Where you are now: architecture, processes, the things that scare you in production
- Where you want to get to: the goal, the constraints, the deadline
- The symptoms: what's hurting today, and how often
What you walk away with
- A technical read on the problem, not generic advice
- A concrete next step — whether it involves me or not
- An honest answer: yes I can help, or no I can't.
The method
Three pillars in a deliberate order. Each builds on the previous. The order is not a detail — it's the difference between building and rebuilding.
Design
— System Design & ArchitectureWhy this order
Architectural decisions are the most expensive ones to change later. They come first: if the foundation is wrong, anything you build on top of it inherits the problem.
Progettazione di architetture software scalabili: microservizi, event-driven, CQRS, API design. Dal requisito al diagramma, dal diagramma al codice. Esperienza con .NET, Go, Kafka, PostgreSQL e sistemi distribuiti.
From the blog
Verify
— Observability & SecurityWhy this order
Once it's designed, you need to know it actually works. Under load, under attack, over time. Without verification, automating just means amplifying the failures.
Implementazione di stack di observability con OpenTelemetry e Grafana (Loki, Tempo, Mimir). Setup di identity management con Keycloak, OAuth 2.0 e OpenID Connect. Visibilità e sicurezza per i tuoi sistemi distribuiti.
Case study
- Observability con OpenTelemetry Più team applicativi senza una baseline comune di osservabilità: ognuno aveva la propria combinazione di log, metriche e dashboard — quando qualcosa andava storto, mettere insieme i pezzi richiedeva ore.
- Adozione Keycloak su Backend .NET Un backend .NET con autenticazione gestita in casa: logica di sessione sparpagliata nel codice, niente standard per l'integrazione di nuovi client, e nessuna risposta chiara quando arrivava la domanda 'come gestiamo SSO o servizi terzi?'
From the blog
Automate
— Pipeline & AutomazioneWhy this order
Only after designing and verifying. Automation amplifies everything sitting above it — mistakes included. That's why it's the last step, not the first.
CI/CD, Infrastructure as Code, GitOps. Automatizzazione di build, test e deploy per ridurre il time-to-production e aumentare l’affidabilità. Esperienza con Jenkins, GitHub Actions, ArgoCD, Terraform/OpenTofu, Ansible e Kubernetes.
From the blog
- RTK and tokensave: reducing token costs in AI coding May 27, 2026
- Playwright: Page Object Model for Maintainable Tests Mar 5, 2026
Why the order matters
What happens when you skip a pillar — or all of them.
| Scenario | What goes wrong |
|---|---|
| Tests without CI/CD | Run by hand, when someone remembers. Eventually, nobody runs them at all. |
| CI/CD without observability | You know the deploy went through. You don't know whether the system actually works. |
| Observability without tests | You see the problems in production, but you can't prevent them. You're stuck in reactive mode. |
| All three together | You design consciously → verify automatically → observe in production. |
Want to talk?
30 minutes to figure out whether we can work together. No commitment, no slides.