Peopleware has been published in 1987 and the reason that it is still as relevant today as it was back then is because of the premise of the book: software development projects fail because of inner failures within the teams that run those projects.
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.
Another story about a small contribution to open-source. This time, I’ve opened a pull request in Kotest to implement generation of HTML reports.
A potentially exaggerated exploration of how Kotlin implements
MutableList, featuring Kotlin’s source code examples.
var forced a mentally shift on me, coming from a background of loosely typed languages, due to what they entails. What is really the difference between
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.
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.