My Tech Pivot

One thing I’ve realized throughout this course is that I actually like to break things. Not because I enjoy failure or frustration, but because breaking things has become one of the best ways for me to learn.

When something stops working, I have to slow down and figure out why. I start retracing my steps, checking configurations, reading logs, reviewing commands, and thinking back to what I learned previously. In those moments, I’m not just following along with a lesson anymore, I’m actively learning how everything connects. Oddly enough, troubleshooting has become one of my favorite parts of learning.

Every time I break something in Linux or Kubernetes, I end up understanding the system better than I did before. Sometimes it’s a typo in a command, a configuration issue, or something I changed without realizing the impact. But each mistake forces me to think critically and apply what I’ve learned instead of simply memorizing steps. I think this is how I know I’m actually learning.

Before, if something broke, I might have felt overwhelmed or immediately looked for the exact answer. Now, I find myself mentally walking through possibilities: What changed? What command did I run? What does this error actually mean? I’m starting to trust the process of troubleshooting. Honestly, there’s something satisfying about finally figuring it out after being stuck.

Learning tech especially Linux, Kubernetes, and infrastructure can feel overwhelming at times. But I’m realizing that progress doesn’t come from everything working perfectly. A lot of growth happens when things go wrong and you have to figure out how to fix them.

So yes, I like to break things.

Because every broken deployment, failed command, or unexpected error usually means I’m about to learn something new.