Aa!

I don’t understand how you got that from the image.

Both monitors on the senior side of the image are showing coding environments

Not quite this, but I did have a validation team that didn’t know when to quit.

The project was a Windows service, and they would be constantly opening bugs saying “program crashes when we deleted xxxxx.dll”

Like… Yeah. If you delete necessary libraries from the installation directory, the program won’t run correctly.

Imagine programming a computer without understanding the machine code that tells the CPU what to do

A couple of main points:

• You are reading tutorials to help you get it up and running. Most of the time these are designed to walk you through setting things up on a fresh node, and most often just VMs on an isolated (trusted) network. When you are providing a guide to just get someone up and running, the first thing to do is establish a known baseline configuration to start from.
• Kubernetes is a complex distributed application, and as such, the audience is generally expected to be relatively experienced. Meaning if you don’t know how to configure your firewall, people assume you aren’t going through this tutorial.

Still, I feel your pain. When trying to get into these technologies, most people who have done the work are engineers, and we stink at writing documentation. I’m sure you’re familiar with it, we automate the solutions for issues we encounter, and then those tools or automatic configurations fail to make it to the end user.

And I’m probably biased, but don’t use a video guide for this sort of thing. It’s just the wrong medium for a technical tutorial.