Over the years, I’ve had the opportunity to work on many projects and see a wide range of approaches to Infrastructure as Code using Terraform. Some of them scaled well, others didn’t. A few worked great early on — but as the project grew, and new resources had to be added under time pressure and shifting priorities, the codebase became harder and harder to maintain. It was still “infrastructure as code”, but each change took longer, and refactoring became too costly to be worth the effort.

Why yet another Gradle plugin

Recently, I wanted to deepen my understanding of Build Scans, Develocity, and their practical applications, so I started going through the courses on our DPE University platform. In my daily work, I interact with Develocity from the operational and production side — maintaining open-source instances among other things — so I wanted to better understand the product, especially from the end-user perspective, to support my daily engineering work.

Welcome to my blog!

I’ve built it to document and share my personal experiences in building solutions for cloud architecture, platform engineering, and AI-native tooling.

It will serve as my personal engineering notebook - a place to capture structured learnings, patterns, and decisions—cleanly and accessibly.

What to expect

• Practical, implementation-focused posts.
• Structured patterns for building scalable platforms.
• Insights on Gradle, OpenTofu, GitOps workflows, and AI-native systems.
• Clean, minimal, and noise-free.

Let’s get started

Instead of leaving you with just a welcome and a list of future topics, I want to share how this blog is set up: fully automated and declaratively managed. Following one of my favourite principles: