Your Brain On Code
The Dangerous Intersection of Today's Software and Our Brains
John Landry | 12X CTO, Serial Software Executive, Angel Investor
Prologue: Our Brains Were Not Built For This
I've been in the software business for fifty-five years. That's every turn in the industry — mainframes, minicomputers, PCs, client-server, the internet, cloud, mobile, and now artificial intelligence. I've been in the middle of all of it, not as an observer but as a builder.
It started almost by accident. In 1971, when I told my father I was getting into the software business, he asked what I knew about women's lingerie. The word didn't mean what it means now. There was no independent software industry — software came bundled with the machine, free, part of the hardware purchase. Then the government forced IBM to unbundle software from hardware, and almost overnight, a new industry was born. The IBM engineers left to start companies, and I got lucky enough to land among them. My degrees were in accounting and finance. Computer science wouldn't exist as a degree for another fourteen years. But I fell in love with the work, and it became my career and my hobby for the next half century.
Software That Did a Job
The systems I built did jobs. They kept the books, paid the bills, exploded parts lists, tracked inventory, optimized warehouse operations, automated the processes that companies ran on. My role was to architect those systems — to determine what the software needed to do, how the pieces fit together, and how the whole thing would work at scale. That's what a CTO at a software company does. You don't write every line of code. You make sure the system does what it's supposed to do.
And what our systems were supposed to do was straightforward: perform a function that the customer needed, perform it reliably, and get out of the way.
Those systems were licensed, purchased, and paid for by the people who used them. They didn't profile their users. They didn't monitor behavior. They didn't decide what information someone should or shouldn't see. If the system performed well, the customer renewed the license and we grew.
And we did grow. The software industry grew, and the companies I helped build typically grew faster than the industry. Six startups, all acquired. Six large enterprises. Forty-three boards. Eighty investments. A career built on systems that worked for the people who used them.
Then something changed.
Software That Did a Job on You
A new generation of software emerged that looked, on the surface, like a natural evolution. Free apps, social networks, search engines, messaging platforms — software delivered as a service, no installation required, no license to buy. It felt like progress. Software was becoming more accessible, more connected, more useful to ordinary people rather than just to corporations.
But underneath that surface, these systems were built on a fundamentally different principle. They didn't do a job for the user. They did a job on the user. They didn't charge for their services — they extracted value from the behavior of the people who used them. And the techniques that made them effective weren't the ones I'd spent my career mastering. They were drawn from neuroscience, behavioral psychology, and a detailed understanding of human cognitive vulnerability that the software industry had never previously needed — or wanted.
This new code learned that the human brain is wired to respond to interruption — and built notification architectures that exploit that wiring hundreds of times per day. It learned that unpredictable rewards create compulsive checking behavior — and designed feeds and content loops that function on the same principle as a slot machine. It learned that emotional provocation holds attention longer than calm information — and built algorithms that systematically amplify content that agitates over content that informs. It learned that removing stopping cues increases consumption — and eliminated every natural signal that might tell you it's time to put the device down.
It learned all of this not through theory but through relentless measurement. Every design choice tested, every variation tracked, every result that increases engagement retained. What emerged was not a collection of popular apps. It was something more coherent and more powerful — a unified architecture of attention capture and behavioral extraction, operating continuously, at planetary scale, across billions of people.
The Machine
I call it The Machine.
Not a metaphor. A machine — with inputs and outputs, running continuously, processing raw material into product. The raw material is your attention, your behavior, your emotions. The product is prediction, targeting, and revenue. It was built from code, but it has become something that no one who writes code for a living would recognize as software. It is an assembly line that takes in human experience and manufactures profit. And it never stops running.
It is not a single app, platform, or company. It is the shared architecture underneath all of them — the notification systems, the recommendation algorithms, the behavioral extraction pipelines, the profiling engines, the ad targeting infrastructure, and the design patterns drawn from neuroscience and behavioral psychology that keep billions of people engaged, monitored, and monetized simultaneously. Different companies operate different surfaces — Facebook, Google, TikTok, Amazon — but beneath those surfaces, The Machine is remarkably consistent. The same loop runs everywhere: capture attention, extract signal, build the model, refine the targeting, hold the user longer, extract more signal.
What Were They Selling?
And The Machine did its job extraordinarily well. So well that it minted the six wealthiest and most powerful people on the planet. Not oil barons. Not bankers. Not industrialists. Software guys — every one of them. Their combined wealth exceeds two trillion dollars.
What were they selling?
They were selling you.
Your attention. Your behavior. Your vulnerabilities. Your future actions — predicted with increasing precision and packaged for whoever was willing to pay. You were never the customer. You were the product. And The Machine that converted you into revenue is the most profitable engine ever built.
That is what I mean by your brain on code.
Not code that helps you think. Code that thinks about you. Code that captures your attention through mechanisms your brain cannot override, extracts signals from behavior you don't know you're generating, builds a model of you more accurate than the judgment of anyone who knows you, and uses that model to shape what you do next — for someone else's profit. Code that operates on your brain the way my old systems operated on a ledger or a warehouse, except you are the raw material, and you didn't agree to the job.
I recognize this architecture because I'm a systems person. I know what good system design looks like and what it's supposed to be for. And what I see in The Machine is not what I spent my career building. It's something else entirely.
Why I Built This
I have grandchildren who can't sit on a beach without staring at their phones. I have friends who don't realize that the posts they share are seen by six people or six hundred — not based on what they wrote, but based on what an algorithm decided would keep someone else scrolling. I carry a device in my pocket that is the most extraordinary piece of industrial design I've ever held, and I don't love it — because I don't trust the software that runs on it.
I built this series because I believe that understanding The Machine is the first step toward not being consumed by it. I'm not writing as a critic from the outside. I'm writing as a systems architect from the inside — someone who has spent a lifetime building large, complex systems and who can see, in The Machine, an architecture that uses the craft I love for purposes I never imagined.
You don't have to throw your phone away. But you deserve to know what it's doing while you're holding it.
What This Series Is
This series is an attempt to map The Machine — not as a collection of products or companies, but as a single structure with identifiable parts.
How it exploits a vulnerability your brain can't patch. Why it was built this way. What it constructs from your behavior. Who controls the surface between you and everything digital. What happens when The Machine accumulates enough power to reshape what people believe is real. And what is about to change when AI begins to undermine the very signals The Machine depends on.
You may not be able to step outside The Machine entirely. But once you see it clearly — as a system, with structure and incentives — you can begin to understand what it is optimizing for, and what that means for you.
Where to Start
Read in order:
- Your Brain Was Not Built for This
- Two Business Models. One Won.
- The Machine: Engagement In, Extraction Out
- What The Machine Builds About You
- Apple Doesn't Compete. It Decides. — Enabling The Machine
- The Machine at Planetary Scale
- When The Machine Becomes Power
- What The Machine Does to Reality
- The Machine Between Us
- AI Is About to Break The Machine That Built It
- The Internet Is Starting to Eat Itself
- How to Become Less Legible to The Machine
A Personal Note
I’ve always been more interested in systems than in software itself. The most interesting systems are the ones that don’t physically exist — the ones you design in your head, then bring to life through code and interaction. That’s what I’ve spent my career doing.
What you’re looking at here is an attempt to reverse that process — to take one of the largest systems ever built, one that most people experience but few understand, and make its structure visible.
Once you see it, you can’t unsee it.