A summary of the principles behind increasing flow of work, along with some of its practices, such as automating infrastructure, automated testing, deployment pipelines and continuous integration.
I like to build and break things. Lately, I’ve been working on tools that improve developer’s lives and productivity. Sometimes I also dabble in automating stuff and optimizing infrastructure. These days I write Python, Go and Kotlin.
A quick exploration of RFC3986 (“Uniform Resource Identifier (URI): Generic Syntax”) Section 3.4.
An exploration behind the reasons why we shouldn’t use statements based on scope function, in particular
let, as if-else checks to validate nullability in Kotlin.
A quick introduction to
check functions, as well as examples of how and why we should use them.
Last January 15th, Signal had an outage of epic proportions. A surge in new users using Signal along with some infrastructure and software issues seems to have broken it. When these things happen, what is left to users?
A recap of the Three Ways of DevOps, as seen in the DevOps Handbook. In this essay we’ll go through The Principles of Flow, The Principles of Feedback and The Principles of Continual Learning, and what they represent in DevOps.
A powerful, vibrant and eclectic debut album from a young Immanuel Wilkins.
In this essay I go through a few steps that describe how to implement a read-only private Terraform registry, serving custom providers privately to be used with Terraform, using Python and Flask.
A Git sub-command and a Git alias I use on a daily basis to help me keep sane and organize local copies of Git repositories.
Great software engineers are difficult to characterize. All of us want to - most likely - be one, few of us get to a stage where our peers recognize us as such. In order to be able to be a great software engineer, we need to understand what is a great software engineer. In order to understand what great software engineers are, we need to understand what characterizes them.