After 4 years of daily driving Arch Linux, I’m leaving. You may think I’m leaving because Arch Linux breaks often. Or because it’s unstable. But the reason why I’m leaving is actually very different. I’m going to be running my workflow like a Kubernetes cluster. I want a workflow where I can throw my laptop in the sea and restore it on a new machine in 10 minutes. And in this newsletter I’ll explain how I’m going to build the workflow of my dreams, and why I have to leave Arch to do this. I will teach you about modern software deployment practices and how you can apply them to your own setup as well. Let’s dive in. Backups What would happen if your main laptop or workstation would die right now? Would you panic? Do you have any backups of your most important files? How fast could you rebuild your system exactly as it was? Could you do it under an hour? Most people, even senior DevOps engineers, would not have any structured backups of their machine, and they would need at least a day to rebuild their computer. I’m doing something most people don’t do. I’m applying the same principles we use for managing server infrastructure to my personal computer. Infrastructure as Code. Immutable systems. Containerization. Stateless workstations. These concepts come from managing Kubernetes clusters and cloud infrastructure. But what if you applied them to your laptop? That’s what I’m testing over the next few months. Why I’m Doing This: KubeCraft is going places. We’ve rented an office space so me and my brother can work together. I need my work environment available on multiple machines now - one at home, one at the office, and my travel laptop for when I’m working from my camper van across Europe. I’ve been organizing things with that goal in mind, but I’ve never actually tested whether it works. Over the next 2 months, I’m going to document building what I’m calling a stateless workstation. It’s the same concept as stateless services in Kubernetes - nothing important lives only on the machine itself.

We all got exposure to DevOps at some point. Some as software engineers, some as sysadmins, and some from completely non-technical backgrounds. I share the story of how I went from nurse to DevOps in the DevOps Blueprint in the Classroom, Image #2 has something to do with it. Do you know what it is? But I want to hear your story. At what point did you decide that DevOps is the thing you want to pursue?

Hi friends, May I ask you a question? Please post in the comments where you are from. This way, we can see where all the members live. Afterward, take a look through the comments and feel free to like or say "hi" to members who are from your area. I'm super curious to see where you're all from and will read every single comment. Let's gooooo! - Mischa 🫡

This post is for everyone who's still on levels 1 to 3. Go on, say hello :-) Anyone who's level 4 or higher is only allowed to use the reply function. Let's see if this works here -Mischa

It's Monday right now 🚀 What are your plans for scaling up your DevOps career in the next couple of days? If you don't have any plans yet, come up with one. 💡 💬 Comment below! (My answer will be in the comments.)