A few weeks ago I was discussing with a customer care agent at Ricardo how to handle certain requests. This discussion made me realize how much jargon we engineers are using when talking about work and how this is an obstacle for other people to understand what we do, but also it’s a hurdle for newcomers to get into this field of work. Part of the engineering culture at Ricardo is to openly share what we’ve learned and transparency. Because of that every Monday I craft a summary post in our general Slack channel summarizing what the SRE team achieved, what were are working on, and what we’ve learned. People appreciate the insights into SRE but I also often got the feedback from that the language used is very domain specific and hard to understand. Apart from trying to use a more approachable language in general, I started to write short explanations for terms we are using as part of this newsletter. I’ve been looking for a little project to refresh my Rails knowledge for a while and this seemed like a good idea, thus the idea for Gobbledygook was born. I hope that this (albeit small) collection of jargon explained might be useful for others. Technology used and learned: Rails 6.1 (devise, ransack, rolify, and pundit) Webpack and Yarn Bootstrap 4 Sendgrid for sending Emails Docker / Docker-Compose Heroku for dev & testing Build & deployment on a Digitalocean droplet
This post explains the adjustments that were needed to the way we work in the SRE Team at Ricardo when we went fully remote.
How traveling the Americas shaped my views of Ops, SRE & the World.
Constructing proper PromQL queries for you data is hard. One tool that helps a lot to understand the data that is available and to construct queries is PromLens. If you don’t know PromLens yet, I suggest to read this blog post. A few days ago we open-sourced the Helm Chart we use at Ricardo to deploy PromLens and we’ve made it available on Artifacthub. I hope this Chart will be as useful to you as it is to us.