Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Owned by Mischa

KubeCraft (Free)

11.1k members • Free

Only for DevOps Engineers Get hired to build the future Use the Community, Blueprint and the KubeCraft Roadmap

KubeCraft Career Accelerator

829 members • $4,800/year

Join KubeCraft to go from Stuck to Hired ♾️ Upskill with job-ready projects, expert coaching and a proven system to land 6-figure roles.

Memberships

Calvin Hollywood

101 members • Free

292 contributions to KubeCraft (Free)
The Skill That Separates $50K Admins From $200K Engineers
I’ve interviewed DevOps candidates who couldn’t rename 30 files at once. They had AWS certifications. They had Kubernetes experience. They had years on their resume. But when I asked them to automate a simple task without Google, they froze. ​ Here’s the truth most people won’t tell you: Many "DevOps engineers" today are just professional button clickers. They know where the buttons are in the AWS console. They can copy-paste commands from Stack Overflow. But they don't know how to use Bash properly. They are not able to write shell scripts. ​ This single weakness is keeping them stuck at $80K while others make $200K doing the same job title. ​ You Are Using Your Computer Wrong Think about how you interact with your computer right now. You point. You click. You drag. You drop. You repeat the same 47-step process every time you need to do something. Computers were invented to free humans from repetitive labor. Instead, we’ve turned them into elaborate pointing-and-clicking machines. Every time you click something, you’re doing a computer’s job for it. Every time you manually repeat a task, you’re trading your time for laziness. Every time you can’t automate something, you reveal a fundamental gap in your skill set. And hiring managers see it immediately. ​ The Power That Cannot Be Faked When I was a Junior DevOps Engineer, I watched a senior solve in 10 seconds what took me 2 hours. He didn’t install a special tool. He didn’t use a fancy GUI application. He typed a single line of bash. My jaw dropped. I asked him immediately if he could teach me. That moment changed my career. ​ The command line provides capabilities that no graphical interface can match. Rename 500 files based on patterns? One line. Find every log file containing a specific error across 20 servers? One line. Transform data, filter it, and pipe it to another tool? One line. Automate a deployment that takes 45 minutes by hand? One script. This kind of power cannot be replicated in a GUI. Ever. Once you experience it, you can never go back to clicking.
This Is Why Real DevOps Skills Beat Tutorials Every Time
In a single day 3 KubeCraft Career Accelerator members shared landing roles. From Junior all the way to Lead SRE. Here's what they had in common so you can learn from it: - None of them relied on watching tutorials, asking ChatGPT for quick answers, or copying examples. - They built real environments. Real clusters. Real problems to fix. - When interviewers asked about Kubernetes troubleshooting or GitOps workflows, they didn’t speak in theory. They walked through actual incidents from their own setups. What broke. Why it broke. How they fixed it. - They knew in advance what would happen, how it would go and what to respond. - They followed a proven, system-backed structure. This cuts results to weeks instead of years of confusion and stress. The same mindset you use in production is the one you develop when you’re building your own systems from scratch. One member said: “The homelab helped me land interviews, but the lifestyle of constant improvement is what changed me.” Some people think the homelab is 'just' for the resume.. It’s not. It rewires how you think. A way of thinking thats actually valued by the job market. For those who missed it, Here's how you can build a Kubernetes Homelab in 30 minutes: https://youtu.be/NkM6wQL2UvM Want to ride the next hiring wave coming up next month? We have 4 spots left for this month. You can apply at www.kubecraft.dev
This Is Why Real DevOps Skills Beat Tutorials Every Time
I have a free gift for you
Hello friends, I've been posting a lot about Kubernetes recently. For example in this previous newsletter, I explained how it is the path to a $171K remote job (on average) and how it can lead to a life of complete independence as a freelancer and business owner. I've gotten extremely positive feedback on these posts. But I also received a lot of questions. The main one being: how do I start? How do I begin learning Kubernetes? ​ To address this question, I decided to build a free course that will help people get started on their Kubernetes journey. It's called the 7-Day Kubernetes Quickstart. And because you are a valued member of the KubeCraft newsletter, I'm giving you early access before anyone else. You can claim your free course here: >> CLICK HERE << Just use the same email that you received this mail on. ​ Enjoy your free course, and see you next week! Mischa
After 4 years of daily driving Arch Linux, I’m leaving.
Not for the reasons you’d expect. I’m applying DevOps principles to my personal workflow: treating my workstations like Kubernetes clusters. Watch my latest video right here to find out more: https://youtu.be/gxWgceGx5Os
After 4 years of daily driving Arch Linux, I’m leaving.
5 likes • 21d
Transcript: (00:00) After 4 years of daily driving Arch Linux, I'm leaving. And 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 to a new machine in 10 minutes. (00:21) And in this video, 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. So, let's dive in. I'll start by explaining why I'm actually doing this. You see, CubeCraft, my business, is actually going places. (00:42) It is growing fast and we're doing really well. So, me and my brother, who is my co-founder, we actually decided to rent an office space where we can build an even more professional studio to create YouTube videos and to collaborate together. So, this is really exciting, but this also means that my trusted little setup here is going to be moving elsewhere and that I'm going to be working from several places now. (01:06) So, I need my workflow to be available here at home when I'm in the office, but also when I'm traveling around Europe in my camper van because I have that remote location freedom right now as a business owner. So, my workflow needs to be optimized for this. And obviously when you set up a new office and a new studio, you also need to buy new hardware. (01:27) And this has been a bit of a process where me and my brother were thinking, what are we going to get? My brother is more of a computer normie, whereas I preferably want to run everything on Linux. So I decided to go for framework. Framework is a company that creates laptops, which is completely aligned with my values and what I like to see. (01:48) So you configure once, upgrade whenever. It's a modular system and you just create your laptop and you can replace your parts. You have the right to repair. You have control over your system. And this is completely up my street. I love this. I'm tired of paying $2,000 for one terabyte of storage on a MacBook.
So you have a home lab. Now what?
One of the questions I get often is: so I built my home lab. What do I do with it? And it’s one of my favorite questions to answer. Every week I host several live Q&A calls in KubeCraft. And this question comes up regularly. During these mentorship sessions, I teach my students a process that you won't find anywhere else. So instead of just giving you a list of apps to run, I’ll share my whole thought process so you can decide for yourself. I think that will serve you better than a list of apps. ​ But before we jump in, I should let you know that I'm only accepting 10 new students in December. If you want to get direct mentorship from me, CLICK HERE to claim your spot. I'll help you land a remote, 6-figure DevOps job so you can live the life of your dreams. ​ What is a home lab anyway? First of all, let’s think about what a home lab is. One big misconception people have is that home labs need to be big server racks with thousands of dollars of equipment. They think you need to run 5 node Kubernetes clusters before you can even call it a home lab. This is completely false. My home lab started with a ThinkPad T430. An old laptop that was gathering dust in a closet. I installed Linux on there, and ran Linkding in a Docker container. I was so proud. I had my own little application that I could run. I was self-hosting. And it all started from there. ​ Solve Problems You Already Have When I get the question, “what should I run?”, my first reaction is always to solve problems you already have in your life. The reason why I ended up self-hosting Linkding was because I was switching browsers so often. I would sometimes have three different browsers running. One on my phone, one on my laptop, and one on my main workstation. I needed a place to store my bookmarks that was independent of the browser. And after using Raindrop for a while, I somehow discovered Linkding. I’ve been using it for over 3 years now.
So you have a home lab. Now what?
1-10 of 292
Mischa van den Burg
7
546points to level up
@mischa
I help people land six figure DevOps jobs with a proven system. Owner of KubeCraft.

Active 13h ago
Joined May 8, 2024
INTJ
Powered by