There exists a rare breed of tech enthusiast who, upon launching Docker for the first time, does not run screaming at the sight of YAML. These are the chosen ones who stare into an endless abyss of containers within containers, pretend networks, and logs that read like Shakespeare after a head injury, and think, “Ah, perfection.” Most rational people would close their laptops and retreat to the safe embrace of Candy Crush. But for a select few, usually left unsupervised for too long, this is where the fun begins. If you were expecting a Marvel origin story, forget it. This is not a workshop built by Tony Stark. It is closer to an outtake from The IT Crowd with worse lighting.
A Perfectly Fine Laptop That Did Nothing Wrong
My own journey starts with a device that deserves its own low budget documentary: the Acer Aspire V3-571-32374G75Ma Olympic Edition. At the time, it felt like holding the future. In reality, it was more like holding a polite suggestion of a computer. Windows 7 ran on it most of the time. It had a special talent for behaving perfectly until the exact moment you needed it, at which point it would collapse into a blue screen like it was auditioning for a drama series. What it lacked in reliability, it made up for in freedom. Give a curious person a fragile machine and you do not get careful experimentation. You get someone pressing every button just to see what breaks.
This Definitely Seemed Like a Good Idea at the Time
That curiosity scaled quickly when I found myself in a school computer lab. Rows of identical PCs, all built on the assumption that nothing unusual would happen. That assumption did not last. At some point, driven by boredom and questionable judgment, I created a script that did not just stop explorer.exe. It deleted it entirely. For context, explorer.exe is what makes Microsoft Windows feel like Windows. Remove it, and the system does not degrade gracefully. It collapses. The script itself was simple. The delivery was the interesting part. I renamed it “Google Chrome” and gave it a convincing icon. It was a low effort move with surprisingly high success.
The result was predictable. Computers froze, desktops disappeared, and the room shifted from routine to confusion in under a minute. It was not a heist. It was closer to watching a group of people slowly realize their environment no longer works. At the time, I thought of it as a neat trick. Now it is easier to name. It was social engineering. Basic, unsophisticated, and effective.
A Login Page That Should Have Been Illegal
That should have been enough.
It was not.
Later, I came across something quieter but far more serious. Access to the school’s administrative system. The place where grades lived, where records were stored, where small changes could have real consequences. There was no elaborate security. No cinematic hacking sequence like The Matrix. Just a login page and credentials that read admin/admin. It was almost insulting.
This was different. Not chaotic, not loud, not accidental. Just a quiet realization that I could change things if I wanted to. And this is where the story becomes disappointingly uneventful. I did nothing. No grades changed, no data touched. I closed the tab and moved on. It was not dramatic, but it mattered more than anything I broke before.
Curiosity Is a Terrible Role Model
Curiosity is often treated as a virtue. Something associated with intelligence, creativity, or ambition. That version is incomplete. Curiosity is neutral. It does not care whether you are building something or breaking it. It only asks what happens if you go one step further. The environment decides how safe that step is. You decide whether to take it.
In my case, the environment made it easy. I had access to systems, friction in how they behaved, and just enough distance from consequences to experiment freely. That combination does not just create curiosity. It reinforces it.
The Homelab That Nobody Asked For
Fast forward to now, and everything looks more structured from the outside. Instead of one unreliable laptop, there is a small network of machines. Instead of breaking Windows, I deploy services that occasionally break themselves. Containers run, fail, restart, and sometimes refuse to cooperate for reasons that require hours to understand. There is a homelab, which sounds more professional than it really is. In practice, it is a collection of devices I refuse to turn off because I want to see what happens next.
There is no real need to self host most of this. Better alternatives exist. More stable, more efficient, maintained by people who actually know what they are doing. Running everything locally is like baking bread from scratch while living next to a bakery. It is slower, messier, and occasionally produces worse results. But it offers something else. Control. Visibility. The ability to understand the system beyond the surface.
Same Behavior, Better Marketing
From the outside, it might look like progress. From chaos to structure, from breaking systems to building them. That is not entirely true. The behavior did not change. It just found a better environment. The same instinct that deleted system files now deploys services and tests how they fail. The same curiosity is still there. It just has better tools.
The Only Upgrade Was Self Control
That is probably the most honest conclusion. Curiosity was not inherited or taught. It was built through access, shaped by friction, and defined by moments where the difference between “can” and “should” became clear.
The kid who disguised a destructive script as a browser is still here. The only difference is that now the systems are mine.
And the question never really goes away.
What happens if I push this one step further?