useful stuff...

In my current company we have a program called 4DWW (4 Days Working Week). It lasts 3 months in the summer, and - as the name suggests - you get in the working week a paid day to do what you want. It was the first time for me, and I have to admit I really enjoy it. Actually this perks was among the decision points that push me to join the company, and I think, in retrospective, it was very successful.

With this article I'm going to share a pattern I come up with, that I've named "Data Contracts Terraform/Kubernetes". We successfully introduced this pattern and it makes the life easier for Platform Engineers and internal customers of such platform.

The more I'm using Kubernetes the more I'm puzzled about the direction we are going. Kubernetes is an excellent abstraction layer over a pre-existing

A bit of context In the company I’m currently working, we develop a multitude of product with diverse requirements and various technologies. If the “one size fit all” never applies to the reality that is even more true for the landscape of my company that successfully span across 30 years of

Dependencies across Developer and Platform teams is a foreseeable challenge you have to take into account when you plan and design a Platform Engineering layer in your company.

Platform Engineering is becoming the new buzzword in our world. At the same time also there are multiple shifts in the tasks for an engineer exposed to production: until a while ago, there was the so called "DevOps engineer", and the role - initially covered by evolved system engineers - was

Terraform variables interface with optionalsThe importante of interface and variable files in TerraformFlexible interfaces in Terraform

Current state of the art We all know, Terraform is the current de-facto standard when it comes to describe your infrastructure.

Summary oAuth2Proxy is a nice component for Kubernetes that adds an authentication layer, transparently, on top of your workload.