Hey Ala,

Yesterday I showed you why skills alone aren’t enough.

The market really hires on three things:

• Skills
• Proof
• Environment

You’ve mostly been working on the first one.

Today I want to talk about the third: environment.
Because this is the one that quietly kills the most careers.

How I learned this the hard way

When I started my journey I was doing it completely alone. Just me and Google.
ChatGPT didn’t even exist yet.

I didn’t have a mentor. I didn’t have a community.

I tried finding people on Reddit, but as I wrote earlier, that became one of the most disappointing experiences of my life.

So I kept grinding alone. Luckily I’m introverted and can be very disciplined for long periods. But it was painful.

When I landed my first job there was a ramp‑up period where I was expected to study Linux and Ansible for a couple of months.

That’s when I discovered I was starting with another junior on the team.

We connected and started learning together, and this completely changed my approach to learning forever.

Instead of hours of Googling, I now had someone on the same level I could talk to.
Whenever I got stuck, I asked:

Sometimes he’d say:

And you’d be amazed how quickly you can solve something simply through the act of conversation.

In programming this is called pair programming. It works just as well for studying.

These days, whenever I’m learning something new, I look for someone on the same journey.
Combine that with a note‑taking system and you learn way faster.

That’s how I went from junior DevOps to Kubernetes consultant and six‑figure salaries in such a short time.

What trying to do this alone actually looks like

• It’s 11:07 pm
• You’ve worked all day
• You open your laptop to “just fix this one error”
• Three hours later you’re still staring at the same error
• ChatGPT going in circles, YouTube videos half‑watched, docs open in six places

And the thought creeps in:

The problem is not that you’re dumb.

The problem is you’re trying to build a very complex skillset inside a vacuum.

No feedback.
No one to sanity‑check your thinking.
No one to say “you’re 90% there, you just missed this one tiny flag.”

What it looks like with a real environment

Contrast that with what I see inside KubeCraft every day:

• Someone posts a screenshot of a failing pod or weird node state
• Another member or mentor jumps in:
  • “Check this log”
  • “Describe the service, not just the deployment”
  • “You’re using the wrong context”
• 5–10 minutes later, it’s fixed

Same error.
4 hours alone vs 5 minutes with help.

Multiply that by hundreds of errors over a year.

It’s the difference between:

• Still “learning Kubernetes” after 18 months
• Versus being job‑ready in 4–6 months with the same raw hours

This is why self‑paced course completion rates are around 3–5%.

It’s not that the content is bad.
It’s that there’s no environment to keep you moving when your brain wants to tap out.

You can do it alone. The question is: should you?

You absolutely can figure this out solo.

If you’re stubborn enough, you can grind:

• 12–24 months
• Hundreds of hours of docs, errors, and random videos
• Dozens of dead‑end rabbit holes

and eventually assemble something that works.

That’s what I did early in my career.
It worked. It just cost me years and hundreds of thousands in lost income.

The real question isn’t “Can I do this alone?”​
It’s:

Because every month you spend:

• Fixing problems other people already solved
• Re‑inventing learning systems that already exist
• Re‑creating interview prep that’s been battle‑tested a hundred times

…is a month you’re not getting paid for these skills.

Today’s action: audit your environment

Open Obsidian.

Create a note called: “My DevOps Environment – Reality Check”.

Write down, honestly, what you currently have in each category:

1. Mentorship
   • Who can you message when you’re stuck on a Linux / containers / Kubernetes issue?
   • How fast do they typically respond?
2. Peers
   • How many people are on the same journey as you, where you regularly share wins, stuck points, and progress?
3. Accountability
   • Who notices if you disappear for a week?
   • Who would ask “hey, what happened to your homelab work?”
4. Feedback
   • Who has looked at your CV, your GitHub, your homelab architecture, and said “this is good / this needs work”?

If your honest answers look like:

• Mentorship: “YouTube, Google, maybe a random Discord”
• Peers: “None, really”
• Accountability: “Just me”
• Feedback: “No one”

…then your environment score is very low, no matter how many courses you’re taking.

That doesn’t make you bad.
It just explains why progress feels so slow and fragile.

Over the next emails, I’m going to show you how people like you:

• Built proof (homelabs, projects)
• Increased their visibility
• And used the right environment

to go from “stuck in tutorial hell” to “I’m signing a DevOps / Kubernetes offer.”

For today, just be brutally honest about the container you’re trying to grow in.

Skills matter.
Proof matters.
But the environment you build those in is the multiplier on everything else.

Talk tomorrow,

Mischa

​

P.S. KubeCraft exists because I couldn’t find this environment when I started. It’s 800+ engineers and mentors all solving the same kinds of problems you’re facing now. No pressure to join – but if you ever decide you’re done doing this alone, you’ll know where to find us.​

​