ABEND dump #3
Tags: news, programming, newsletter
Published: 2022-12-16 18:15:52

Hi there, welcome to the [ABEND dump](https://bitmaybewise.substack.com/i/68092102/what-is-abend-dump)! The issue where I share the most interesting content I’ve been reading, listening to, and watching lately.

Want to check the previous issue? Read it here: [ABEND dump #2](https://bitmaybewise.substack.com/p/abend-dump-2)

##[Advent of YARV](https://kddnewton.com/2022/11/30/advent-of-yarv-part-0.html)

Are you into advent calendars? And Ruby? And low-level code? All of them? So…

For those unaware, YARV stands for “Yet Another Ruby Virtual Machine”. It is the virtual machine used by CRuby.

[Kevin Newton](https://twitter.com/kddnewton) is doing an amazing job of documenting the YARV instructions.

##[Ruby, multidimensional arrays, and mutability](https://bitmaybewise.substack.com/p/ruby-multidimensional-arrays-and)

My latest publication. The title is already spoiling the content.

##[How we diagnosed and resolved Redis latency spikes with BPF and other tools](https://about.gitlab.com/blog/2022/11/28/how-we-diagnosed-and-resolved-redis-latency-spikes/)

[Matt Smiley](https://gitlab.com/msmiley) goes down the rabbit hole in this thorough analysis of how Redis latency spikes were impacting GitLab and what the team has done to solve it. An impressively detailed technical article.

Are you into technical analysis from the inside out? Then this is for you, don’t miss it!

##[Dealing with Metrics at Scale at GitLab](https://youtu.be/2zL9DymXi1E)

In this insightful talk, [Andrew Newdigate](https://gitlab.com/andrewn) explains how metrics are used at scale at GitLab, and how to manage the noise.

##[Awesome SLOs](https://github.com/steveazz/awesome-slo)

Lately, SLAs, SLOs, and SLIs became part of my routine work.

SLA = service level agreement, SLO = service level objective, SLI = service level indicator.

[Steve Azzopardi](https://github.com/steveazz) started curating a repository called [awesome-slo](https://github.com/steveazz/awesome-slo), which is super useful as it aggregates a lot of great related content about the topic, and is a good complement to the [Google SRE books](https://sre.google/books/). I’m bookmarking it.

##[Split Your Overwhelmed Teams](https://queue.acm.org/detail.cfm?id=3570920)

In this article, Thomas Limoncelli digresses how the cognitive load is detrimental to teams, especially in bigger teams, and makes a case for splitting the overwhelmed team members into multiple teams.

TLDR, it’s kinda obvious that splitting a big team into smaller teams will lead to more efficient communication within the team, easier consensus, fewer meetings, and clear goals. What made me think was a need for repetition. Reflecting back on the past, I always caught myself sticking to at least one task or activity that I had to practice often, even though for short time frames over the week, but I’ve been in situations where I saw colleagues struggling to make sense of it and find purpose. So, food for thought!

---

If you liked this post, consider subscribing to my newsletter [Bit Maybe Wise](http://bitmaybewise.com/).

You can also follow me on [Twitter](https://twitter.com/bitmaybewise) and [Mastodon](https://mastodon.online/@bitmaybewise).

---

Photo by [Luke Chesser](https://unsplash.com/@lukechesser) on [Unsplash](https://unsplash.com/)