CTO's reading list ed.2
I was finally able to build the fourkeys project I mentioned in my last article. I will soon share some metrics for Lykon on how this project is helping us become a more efficient tech department. Maybe I can also open source it in case someone would be interested in checking it out.
This week I’ve also been looking into Rust more in depth. Trying to understand how it works, it’s ecosystem, and how it performs when compared to Go. I don’t intend to change Go for Rust, but I’d like to understand it better and maybe, in the future, use it for something.
Let’s dive into this week’s picks. ✍️
An amazing review of how Monzo does autoscaling in their Kubernetes infrastructure. Monzo is one the references I always like to look when dealing complex Kubernetes set ups. Definitely worth a reading.
This week we had the state of devops report from puppet release. It’s an interesting research, and I think it’s worth reading it. It shows how the industry is evolving on understanding the devops culture.
I always like to talk about, what does being a Senior Engineer actually is about? This article here summarizes a lot of things that I agree on, and I think every Sr. Engineer should strive to have. And what I also like about this post is the terminology of a mature Engineer. That’s a great way of determine wether someone (being a senior engineer or not) has the emotional inteligence to deal with certain topics.
Ah, the beauty of algorithms. This week I started re-reading this amazing piece of art. Doesn’t matter if you are an experienced developer, or just started studying Computer Science, or a curious person. This books is for everyone. You’ll have the opportunity to learn about the Big O notation, and how to properly use it. You’ll dive into the mysteries of graphs, and trees. The book is very didactic and easy to follow. Go ahead and read it, you’ll love it!
Thank you for reading! Have some feedback? – Just send me a DM.
See you in the next article 👋