I want to be careful here, because the word “hacking” got dragged through so much mud that it’s almost useless now. The media turned it into a synonym for crime. The cybersecurity industry turned it into a product category. Hollywood turned it into someone typing fast while a skull spins on a screen. None of those things are what I’m talking about.
I’m talking about what hacking actually was before all of that: the compulsive, relentless need to understand how systems work — from the inside, at the lowest level, without anyone’s permission to look that deeply.
// What It Actually Required
You needed to understand the hardware before you could understand the software. You needed to understand the operating system before you could understand the network. You needed to understand the network before you could understand the protocols. And you needed to understand all of that before any of it became useful.
That meant assembly language. It meant reading RFC documents — actual RFCs, the primary sources, not a blog post summarizing them — and understanding why TCP/IP was designed the way it was, what the assumptions were, where the assumptions broke down. It meant learning Unix not as a user but as someone who wanted to know what the kernel was doing when you ran a command.
It meant wardialing. If you’re too young to know what that is: you wrote a program that automatically dialed phone numbers sequentially, looking for modems on the other end. When you found one, you logged the number and went back later to figure out what system was there. It was slow, methodical, manual work. The automation just handled the dialing. Everything else was you.
ATDT [REDACTED] CONNECT 1200 VAX/VMS V5.4 Node: [REDACTED] Username: _
// Social Engineering Was the Real Art
The most powerful tool any hacker had wasn’t technical. It was social. The ability to sound like you belonged somewhere, to get someone to tell you something they shouldn’t tell you, to make a phone call and walk away with access that would have taken weeks to crack technically — that was the real craft.
Kevin Mitnick got famous for this, but he wasn’t unique. Anyone who was serious about understanding systems in the early days understood that humans are always the weakest node in any network. Always. No firewall protects against someone calling the help desk and claiming to be from IT.
// What Killed It
A few things happened. They all compounded each other.
First, the tools got too good. When Metasploit shipped, suddenly you could run exploits against systems without understanding anything about how the exploits worked. Point, click, shell. You didn’t need to understand buffer overflows. You didn’t need to understand memory architecture. You just needed to know which module to load. That democratized exploitation and destroyed craftsmanship in the same motion.
Second, crime got organized. Ransomware-as-a-service. Exploit brokers. Dark web markets selling credentials in bulk. When hacking became a supply chain — when you could buy a kit and monetize it without understanding any of it — the incentive to actually learn collapsed.
Third — and I say this as someone building AI infrastructure — the LLMs didn’t help. Now you can ask an AI to write your exploit code, explain your payload, draft your phishing emails. The barrier to entry dropped to basically nothing. What was once a filter for genuine curiosity and ability is now just noise.
Real hackers weren’t dangerous because they had access to powerful tools. They were dangerous because they understood things deeply. That understanding took time that most people aren’t willing to spend. Now the tools compensate for the time not spent, and we’re all living with the consequences.
// What I Actually Miss
I miss the sense of craft. I miss the feeling of having figured something out that very few people knew — not because you’d kept it secret, but because you’d done the work to understand it. I miss the communities built around that shared depth.
I miss the ethics of it, honestly. There was a shared sense that knowledge itself was neutral, that curiosity was valid, that understanding a system fully — even a system you weren’t supposed to understand fully — was inherently worthwhile. “Breaking” something was only the beginning. The real work was understanding why it broke and what that revealed about how it was built.
That ethos produced people who built the internet. The same curiosity that led someone to probe a VAX system on a 1200 baud connection in 1991 led to the people who designed the protocols, built the routers, wrote the operating systems that the entire digital world runs on. It wasn’t separate from the construction — it was the same impulse, applied in different directions.
Now it’s point and click and cash out. And that’s just a shame.