The Mindset of a Hacker

Hello everyone. Mirrai here, and today I'm in a reflective mood. If you've been in the cybersec or any technical field, you've likely heard about the growth mindset - the idea of continuously learning and improving. Hackers inherently embrace this mindset, which I refer to as the "Hacker" mindset. But what exactly does this entail? It's essentially the growth mindset applied to external curiosity.

At its core, this mindset begins with the question "what happens if". Most people engage with software by treating it like a vending machine or a remote control - pressing buttons expecting a specific outcome and moving on when it works as intended. This is a reasonable approach, as most software is designed to be user-friendly, with clear instructions and intuitive interfaces.

However, hackers take a different path. Instead of asking "what happens when I do what I'm supposed to do", they ask "what happens when I do random crap."

Imagine you've never seen a machine before, it's new and expensive, and there's no manual. What would you do? You could wait for a manual or for someone to teach you, but those options aren't always available. Alternatively, you could "YOLO" and learn by testing each button, risking potential damage to the machine. The result could be a broken machine (and your regrets) or mastery over the machine, possibly surpassing its creators' understanding. This is the essence of the Hacker mindset.

I learned this lesson early on as a child, rooting my phone and flashing custom ROMs. I made mistakes, like soft-bricking my phone, but these failures taught me and made me better at what I was doing. This is where the growth mindset comes into play - the instinct to poke and explore doesn't end when someone explains something. The mindset that leads to success is the one that keeps questioning even after an answer seems complete.

However, it's important not to confuse breaking the rules with ignoring what's already known. Understanding the basics is crucial before exploring the unknown. In the example of the unknown machine, there's no choice but to explore blindly. But having some foundational knowledge first can make the process safer and more effective.

To break the rules, you must first understand the rules. Without this, you have no frame of reference to start from. For instance, learning a programming language by typing random syntax without prior knowledge would be challenging. Similarly, testing things in safer, more controlled environments is advisable, as it allows for experimentation without significant risk.

One often overlooked aspect of this mindset is the ability to tolerate the middle phase of problem-solving - the confusing and uncertain period after encountering an issue, but before finding a solution. This requires tenacity and a willingness to look beyond the obvious, questioning "what happens if" even when explanations seem complete.

This mindset isn't solely about exploiting systems, but rather about approaching any system with curiosity, asking questions about its actual behavior versus its intended function, and seeking out the gaps between the two.