The Conscience of a Hacker in the Age of AI

A short essay written by a teenager in 1986, hours after an arrest, has been with me for almost my entire hacker life. I read it as a kid, came back to it as an engineer, and I still recognize myself in it decades later. In the age of AI, it reads less like nostalgia and more like a warning.

The piece is "The Conscience of a Hacker," written by The Mentor and better known as the Hacker Manifesto. Most people who work in technology today have never read it. It sits buried in the archives of the early ASCII internet, a monospace relic from a world of dial-up modems and bulletin boards. But it shaped how many of us thought about systems, power, curiosity, and freedom long before cybersecurity became an industry, and long before "AI governance" was even a phrase.

From roughly 2004 to 2012 I worked as a white-hat hacker. I disclosed flaws in Sun Microsystems' infrastructure and wrote about security for Dziennik Internautów. The habit that stayed with me is simple: inspect the mechanism before trusting the interface. I use the same habit with language models.

What the manifesto actually says

Strip away the teenage defiance and the manifesto makes a precise argument. The author describes being bored by an education system that hands out answers to be memorized rather than understood. He finds a computer, and for the first time something responds to what he does rather than what he is told to accept. The machine does exactly what he asks. It has no hidden agenda he cannot inspect. That is the seduction, and it is not really about crime at all.

The core claim is that curiosity is not a threat. The famous closing line calls curiosity the crime. I read it less as bravado than as a demand to understand systems instead of accepting the answers handed down by them.

The hacker ethos, read carefully, is three commitments. Curiosity as a duty rather than a vice. Skepticism of authority, especially authority that asks to be trusted without showing its work. And a refusal to trust any system you have not first understood from the inside. Those three commitments were forged against phone switches and mainframes. They transfer, almost without modification, to large language models.

Nullius in verba: take nobody's word for it

My motto is nullius in verba, the old line of the Royal Society. Take nobody's word for it. Verify against primary sources. It is the same instinct the manifesto describes, just dressed in Latin instead of leetspeak. And it is the single most important discipline for anyone deploying AI at scale.

A modern language model is the most fluent authority figure ever built. It speaks in the confident register of a textbook, cites plausibly, and never signals doubt unless you force it to. It is, in other words, exactly the kind of authority the hacker ethos teaches you to distrust on principle. Not because it is malicious, but because fluency is not the same as correctness, and a system that cannot show its work has not earned your trust regardless of how well it performs.

The tools changed. The questions didn't. Understand the system before you trust the output; the machine's confidence is not evidence.

This is where the old mindset stops being romantic and becomes operational. If you spent years assuming any system does precisely what its incentives and its code dictate, and nothing more, you already know how to treat a model. You do not ask whether it seems smart. You ask what it is optimizing, what it can see, where it fails silently, and how you would catch it when it does.

The mindset now runs in the products I build

I did not keep this as a philosophy. I wired it into ventures. Two of them are direct descendants of the manifesto's logic, translated from breaking systems to building trustworthy ones.

Lextron.ai exists because a model's answer is a claim, not a fact. It verifies AI output against primary sources rather than letting fluent text stand on its own authority. That is nullius in verba compiled into a pipeline. The machine proposes; the sources dispose. If a claim cannot be traced to something you can independently inspect, it does not get to count as knowledge.

Inclify applies the same skepticism to the physical world. It trusts sensor data over inspection schedules, because a schedule is an assertion of authority ("this was checked, therefore it is fine") while a sensor reading is primary evidence about what is actually happening right now. A calendar says the equipment is safe. The data tells you whether that is true. The hacker instinct is to believe the data.

Both are the same move. Replace inherited trust with verified evidence. Refuse to accept a system's self-report as ground truth. It is the manifesto's suspicion of authority, aimed not at institutions but at the far more seductive authority of a confident machine.

Why this matters more as capability rises

Here is the uncomfortable part. As models approach and possibly exceed human capability across more domains, the temptation to simply defer to them grows in lockstep with their competence. The better the system performs, the more expensive independent verification feels, and the more tempting it becomes to just take its word. That is precisely the moment the hacker ethos becomes non-negotiable rather than nostalgic.

Approaching superintelligence does not retire the question "how do I know this is true." It sharpens it to a point. A system smart enough to be usually right is a system whose rare, confident errors are the most dangerous, because you have been trained by its track record to stop checking. Curiosity and skepticism are not obstacles to progress here. They are the only brakes that scale.

Concretely, the disciplines I would carry forward from the manifesto into any serious AI deployment are these:

• Understand before you trust. Know what the system optimizes, what it can access, and how it fails. A model you cannot describe mechanically is a model you cannot govern.
• Treat fluency as a red flag, not a green light. Confidence is a rhetorical property, not an epistemic one. The smoother the answer, the more it deserves a source.
• Verify against primary evidence. Ground claims in something inspectable. If the chain of evidence breaks, the claim is a hypothesis, not a fact.
• Keep a human in the loop where the loop is load-bearing. Automate the work; do not automate away the accountability. Someone has to be able to answer for the decision.
• Assume the incentive gradient, not the marketing. A system does what it is rewarded to do. Read the reward function, not the press release.

The questions outlived the tools

The manifesto was written against a backdrop of mainframes and prosecutors who could not tell exploration from theft. Almost none of that context survives. The phones are different, the networks are different, the very definition of a computer is different. And yet the mind it describes is the exact mind the AI era rewards: relentlessly curious, congenitally skeptical of authority, unwilling to trust a system it has not taken apart.

That habit leads to two practical questions I keep returning to: how much does independent verification cost, and who decides which systems may act? I develop those questions in verification cost is the new bottleneck and model wars are over, clearance wars begin.

I keep coming back to that old essay not out of sentiment but because it turned out to be a specification. It described the kind of thinking that would be needed decades before the systems that would need it existed. The full map of how this mindset runs through my work lives in the manifest. Forty years on, the manifesto still hits uncomfortably close, and I have stopped being surprised by that. The machines got smarter. The reasons to check their work only got stronger.