#99 Seven-Day DevOps

#99 Seven-Day DevOps


This newsletter is kept sweet and short, focused on my personal learning.

Hello beautiful people,

I hope you are having a good week, and if not, tomorrow is always a new day!

As you might have seen, I am experimenting with a new header. My Labrador Arkady wanted to be included, so I hope her smile made you smile hahah
Otherwise, all the logos included are tools that I am currently using or plan to create more content on.

This newsletter is kept sweet and short, focused on my personal learning.


Manage incidents directly from Slack with Rootly.
Rootly automates manual tasks like creating an incident channel, Jira ticket and Zoom rooms, inviting responders, creating status page updates, postmortem timelines, and more.
Want to see why companies like Canva and Grammarly are using Rootly?

My Go progress

*Side Note: it's more enjoyable than my Rego progress I shared in last week's newsletter.

The best way to learn a programming language is really just to get started and build something that is aligned with your existing skillset of the language.

I built my first Trivy Plugin – the main difficulty was learning how to work with JSON schemas in Go. The plugin can be used to compare two Trivy scan results and see the difference between the scans:


I will soon publish a tutorial on building Plugins for Trivy. At the moment, I am reading through:

Learning Go, 2nd Edition & highly recommend this book (PS. not sponsored)

While I have written Kubernetes Operators in Go before (with the help of co-workers), I have not written many programs from scratch, which is something I am working on. More to come!

Word of the week

"thick client"

I was reading the OWASP "Database Security Cheat Sheet" in preparation for my Cloud Native Rejekts talk & to do additional research – and came across the term "thick client", which I had never heard about before. So naturally, I got curious and looked it up:

Also referred to as desktop, fat, or heavy client, thick clients are systems that connect to servers even without a network. Put simply, a thick client does not rely on server applications since it can process, store and manage data, as well as perform different tasks independently. It is an ideal option, especially in scenarios where the central server has slow network speeds, memory concerns or insufficient power to support client devices, or a need for offline operations. Source

And OWASP is very insistent on the following: "Direct connections should never ever be made from a thick client to the backend database." Source

Additionally, here is a good comparison table.

Talk highlight

EBPF for the rest of us - Federico Paolinelli

Also GoLab has some amazing talks on their YouTube channel:

GoLab conference
This channel is dedicated to the videos of the GoLab conference. GoLab is the first Italian international conference on the Go programming language, organized by Develer. Develer is not just an Italian company projecting and releasing hardware and software solutions for the industrial environment, but is also an ensemble of people sharing their great passion for new technologies and how they can be applied to your everyday life.

Top Meme

Personally, I never thought of it & it's hilarious