GeekCoding101 make your way to geek

Tutorials: Step-by-Step Guides You Can Run Yourself

5 posts on tutorial, newest first.

5posts
2025first post

Every post on this page is a hands-on tutorial: a guide you can follow on your own machine, start to finish, rather than an overview. Posts are listed newest first and cover Go and Kubernetes so far, with more added as they’re written.

Where to start

If you want to…Start withRead time
Build your own Kubernetes lab at homeKubernetes Tutorial Part 1: Multi-Node Cluster on a Mac22 min
Fix a Go loop that keeps returning the same pointerGolang Range Loop Reference – Why Your Loop Keeps Giving You the Same Pointer (and How to Fix It)4 min

Kubernetes Tutorial Part 1: Multi-Node Cluster on a Mac covers the groundwork for a multi-node Kubernetes lab:

  • planning the cluster and its networking
  • creating a Rocky Linux 9 base VM in VMware Fusion
  • preparing the nodes

Golang Range Loop Reference is a short coding note. It starts from a real bug: iterating over a list of Book structs and ending up with the same pointer every time. It explains why that happens and how to fix it.

How these tutorials are written

GeekCoding101 is a hands-on tech blog. The tutorials are written by an engineer with a long background in security and data backup and restore. They come from building and running real systems, and the goal is always steps you can repeat yourself. Every post is free to read, with no sign-up.

FAQ

Are these tutorials free? Yes. Every post on GeekCoding101 is free to read and there is no sign-up.

What do I need for the Kubernetes lab tutorial? Part 1 builds the lab on a Mac, using VMware Fusion to create a Rocky Linux 9 base VM that the cluster nodes are prepared from. The post walks through planning the cluster and its networking before you create anything.

Why does a Go range loop give me the same pointer? Before Go 1.22, the loop variable in for _, v := range items was a single variable reused on every iteration. Taking &v gave you the same address each time. Go 1.22 made that variable per-iteration. Even so, &v points to a copy, not to the element in the slice. To point at the element itself, use &items[i]. The Golang Range Loop Reference post walks through the bug and the fix.

Where can I find tutorials on other topics? Use All topics → to browse every tag, such as coding-notes, devops and kubernetes, or All posts → to see everything on the blog.