Ciao, I'm Giovanni 👋

Software engineer · systems thinker · relentlessly focused on quality

I'm a software engineer based in Naples, Italy, currently working with IASolution.

I do not see software as a frontend connected to a backend. I look at the entire ecosystem: product experience, application code, data, integrations, infrastructure, delivery, runtime behavior, and operations.

For me, a feature is only complete when every layer that supports it has been considered.

UX → Frontend → APIs → Data → Containers → Cluster → Network → Operations

I work across cloud and on-premises environments, choosing the architecture that fits the real constraints rather than following a trend. When the problem calls for it, that includes containerized workloads, Kubernetes orchestration, deployment strategy, and the infrastructure surrounding the application.

The best code is the code I do not have to keep fixing.

I'm obsessed with getting things right. To me, perfection is not endless polishing or unnecessary complexity: it is thinking deeply enough before and during implementation that the result remains dependable after it ships.

That means:

• Treating the happy path as only the beginning
• Anticipating edge cases, failure modes, and operational constraints
• Designing components with clear responsibilities and predictable behavior
• Automating repetitive work and removing avoidable sources of human error
• Optimizing for predictable performance and responsible resource use
• Favoring maintainable solutions that can evolve without fragile rewrites
• Verifying assumptions instead of relying on “it should work”

Software will always evolve. My goal is for code to change because the product has evolved, not because foreseeable cases were ignored the first time.

I work with both relational and non-relational databases. I choose the data model from access patterns, consistency requirements, query behavior, scale, and operational cost, not from habit. Schema design, indexing, efficient queries, and storage footprint are part of the application architecture.

I care deeply about building applications, services, and web platforms that produce strong results with the smallest sensible resource footprint. Performance is not a final polish step: it is an architectural concern.

I optimize across the whole path: algorithms, allocations, database queries, network calls, container images, and runtime configuration. The goal is to reduce CPU and memory consumption without sacrificing correctness, resilience, or maintainability.

• Profile and benchmark before optimizing, then measure the result
• Avoid unnecessary work, allocations, data transfers, and dependencies
• Design efficient data access and control expensive I/O
• Right-size services and infrastructure instead of hiding waste with hardware
• Keep performance behavior observable and predictable under real workloads

Fast software is good. Efficient software that stays correct under pressure is better.

AI is part of my daily workflow. I use it to accelerate research, analysis, debugging, testing, documentation, automation, and repetitive engineering tasks, while keeping architecture, verification, and responsibility firmly human-owned.

I'm a strong supporter of OpenAI and the work they are doing to turn advanced intelligence into practical tools that amplify what people can create. I see AI neither as a shortcut nor a replacement for engineering judgment, but as a force multiplier for curiosity, precision, and execution.

correctness · resilience · efficiency · maintainability · clarity · longevity