Documented experience
Real-world projects, independent work and demonstration labs, with their scope, activities, checks and limitations made explicit. No outcome is attributed to a client unless it is documented.
From context to verification
Each page distinguishes practical project work from technical labs and explains what was checked, what was outside the scope and which supporting materials are available.
An independent project · Linux and DevOps
A website with public pages and an active community needed to become a single platform. The challenge was to bring the new interface online while retaining existing accounts, content and access. This case study covers the documented September 2026 release and the checks carried out alongside it.
Read the project: A web platform on Linux.Client project · Azure · Large-scale retail
For one of Italy's leading large-scale retail businesses, I built an Azure landing zone and oversaw the addition of a range of resources. Alongside the infrastructure work, I guided the client in writing internal standards, documenting processes and making strategic technology decisions.
Read the project: An Azure landing zone.An independent project · DevOps
Updating an application that people already use requires repeatable checks, from reproducing defects to verification after release. This article examines the same independent project covered in the Linux case study: a later revision, documented in September 2026, focused on testing and releasing fixes.
Read the project: A DevOps project.Demonstration lab · Cloud Engineering
This demonstration lab translates an AWS architecture into Terraform code and repeatable checks. It is the same example discussed in the Cloud Architecture article. Here, the focus is on implementation, input constraints and local verification with a mock provider.
Read the project: Cloud Engineering lab.Demonstration lab · Cloud Architecture
This demonstration lab documents the decisions behind a static web architecture: which components to use, how to control origin access and which tasks to leave outside the module. It is the same Terraform example described in the Cloud Engineering article, examined from a design perspective.
Read the project: Cloud Architecture lab.Transparency
Published projects do not disclose client names or confidential details. Labs are clearly identified as demonstrations and kept separate from professional case studies. Where code or verifiable outputs are available, they are linked directly from the project page.
The next step
Let’s start with your current infrastructure, constraints and the outcome you want to achieve.