Back 2 Code

Fun but so true

Some of my favorite quotes about software engineering. Architecture If builders built houses the way programmers built programs, the first woodpecker to come along would destroy civilization. – Gerald Weinberg There are only two hard things in computer science: cache invalidation and naming things. – Phil Karlton Development Don’t comment bad code – rewrite it. – B. W. Kernighan & P. J. Plaugher Refactoring is often compared to gardening; it is never finished.


I explain here how to interact with AWS either with the CLI (Command Line Interface) and with an IT automation tool: Ansible. Ansible is not the first tool that comes in mind for AWS (Serverless, Terraform or the built-in CloudFormation make more sense) however Ansible could be useful if you just want to configure some EC2 and specially if you have already an Ansible script somewhere around.

Chaos Engineering: an introduction

Chaos Engineering. Building Confidence in System Behavior through Experiments

Chaos Engineering is the discipline of experimenting on a distributed system in order to build confidence in the system’s capability to withstand turbulent conditions in production. – Principles of Chaos

Release It!

This book is a bible for any professional who wants to deploy a solution in production–it’s the goal normally, not building throwable POC. It is a recognized reference since it has helped to popularize certain patterns such as the circuit breaker and it is at the top of all the must read lists in the domain. It’s full of good advices and feedbacks since Michael T. Nygard has worked in the field in question, which is now called operations (and even SRE), on critical applications–mainly, but not only, big e-commerce sites.


I’m using Pelican for another blog dedicated to books–no one is perfect. For several needs–an mainly because I’m a nerd–I have developed several plugins. And I have discovered that the Pelican plugin mechanism is based on a small framework called Blinker.

Blinker provides fast & simple object-to-object and broadcast signaling for Python objects.

The 4 Golden Signals + 1

The term 4 golden signals has been introduced by Google SRE team in the book Site Reliability Engineering1. The main definitions presented below are borrowed from this book. The four golden signals of monitoring are latency, traffic, errors, and saturation. If you can only measure four metrics of your user-facing system, focus on these four. 1 - Latency (Performance) The time it takes to service a request, with a focus on distinguishing between the latency of successful requests and the latency of failed requests.