Skip to content

About

I am a backend and platform engineer focused on systems that need to stay maintainable after they leave the prototype stage.

I usually work on the parts of a product that decide how the system will grow: backend structure, API boundaries, runtime behavior, deployment models, data flows, and operational visibility.

I am from Basilicata, in Southern Italy. That background matters to me: it keeps me connected to a territory where technology is often built with limited resources, practical constraints, and a strong need for durable solutions. I bring that same mindset into my engineering work: clear structures, careful trade-offs, and systems that can keep working after the initial excitement is gone.

My interests sit at the intersection of:

  • software architecture
  • runtime systems
  • modular design
  • integration platforms
  • developer tooling
  • cloud-native infrastructure
  • geospatial and data-processing pipelines

I am especially interested in problems where:

  • systems evolve over time
  • components are loaded dynamically
  • environments are heterogeneous
  • failures must be detected early
  • integrations must remain predictable

Background

My background includes:

  • backend development
  • modular frameworks
  • IoT and edge platforms
  • containerized infrastructures
  • integration-heavy systems
  • real-time communication backends

I have worked on projects involving:

  • plugin-based architectures
  • runtime validation engines
  • device integration platforms
  • real-time APIs
  • distributed backend systems
  • infrastructure automation
  • terrain/model-generation pipelines

Rather than defining myself by one framework, I focus on patterns that remain useful across stacks: clear boundaries, explicit contracts, predictable failures, and deployment models that developers can actually run and reason about.

What I Care About

I care about building systems that:

  • are structurally sound
  • fail in understandable ways
  • can evolve without constant rewrites
  • are safe to extend
  • are easy to debug
  • remain maintainable over time

I try to avoid:

  • trendy tools
  • short-lived frameworks
  • fragile abstractions
  • quick hacks that accumulate hidden debt

How I Work

I tend to work:

  • iteratively but deliberately
  • with a strong architectural direction
  • with a focus on invariants and contracts
  • with an emphasis on long-term consequences
  • with attention to operational concerns

I prefer environments where:

  • architecture is valued
  • technical debt is managed intentionally
  • correctness matters
  • reliability is not an afterthought
  • system design is treated seriously

Outside of Code

Outside of software, I am interested in:

  • complex systems in general
  • problem-solving disciplines
  • long-term thinking
  • design philosophy
  • the relationship between structure and creativity
  • the technical and cultural potential of Basilicata and Southern Italy

I enjoy working on projects that require:

  • deep technical reasoning
  • architectural trade-offs
  • conceptual clarity
  • systems thinking

Why This Portfolio Exists

This portfolio is not meant to be only a list of technologies.

It is a collection of case studies showing:

  • what the problem was
  • what I built
  • which architectural decisions mattered
  • how the system was made deployable, observable, and maintainable

Each case study connects design principles to concrete implementation choices.