Madalin
Development enhanced by AI
/i-was-the-gatekeeper

I Was the Gatekeeper

A former tech gatekeeper confronts how AI is democratizing access to once-exclusive skills, revealing uncomfortable truths about gatekeeping, prestige, and what happens when expertise stops being scarce.

Diverse silhouettes of people approaching an open gate in an ancient stone wall, with warm light streaming through and an abandoned guard post in the foreground.

The gate is open now. This one is for everyone who was never allowed through.

Second in a series on what the AI shift actually means for the people who build and run things. Part one: Scribes, Looms, and Compilers.

I need to open with something uncomfortable, because the rest of this article doesn’t work without it.

For years, I was proud of the wrong things. I was proud of the 14-hour days. Proud that I could untangle problems that made other people give up. Proud, quietly, that when someone asked a question I considered basic, I could feel myself looking down before I’d even answered. My income agreed with me, and I took that as proof. Solving hard technical problems paid generously, so clearly the people who couldn’t do it were simply… less. I never said it out loud. I didn’t have to. The whole culture said it for me — the forum answers dripping with contempt, the “read the docs” dismissals, the interview rituals designed to make people feel small.

I was a gatekeeper. A polite one, but the gate doesn’t care about your manners.

In the previous article I walked through five centuries of evidence that fighting a cost collapse never worked. This one is about who’s standing on the other side of the gate — and why I’ve stopped guarding it.

This is not Luddite fear. It’s guild fear.

Let me correct something I got wrong in my own thinking first, because precision matters here.

When highly paid programmers, data analysts, and system administrators worry that AI agents will let “ten more people join the party” and drag a $300K job down to $70K — I understand it, I’ve felt the cold version of that fear myself — but calling it a Luddite reaction is an insult to the Luddites. The Luddites were weavers facing actual destitution. Wage collapse for them meant hungry children, not a smaller house.

What we’re watching today is older than the Luddites and much less sympathetic: it’s guild fear. Medieval guilds kept prices high by keeping supply low — controlling who could enter, who could train, who was allowed to practice. The scribes’ guilds resisting print. Taxi medallion owners fighting ride-sharing. Every professional body that ever made the on-ramp longer than the skill required. The walls were never about quality. They were about scarcity.

I’ll say the honest part: some people in this transition are vulnerable, and they’re not the ones complaining loudest. Junior developers trying to land a first role, people in outsourced positions built entirely on tasks agents now do — they deserve real concern. The senior engineer worried his scarcity premium might normalize does not belong in the same sentence.

Who walks through the open gate

Here’s what actually changed, and it’s bigger than “AI writes code.”

Every previous tool lowered the barrier to doing. An agent lowers the barrier to learning while doing. You can open a terminal today and type, in your own words, in your own language: “I don’t know how to do this. Teach me while we build it together.” And something with infinite patience and zero contempt will do exactly that. No sneering forum. No $15,000 bootcamp. No unpaid internship you can’t afford to take. That has never existed before. It is the printing press moment — literacy and production in one package.

So who was standing outside the gate all this time?

Parents at home. The industry’s real entry fee was never intelligence — it was uninterrupted time. Twelve free hours a day to grind. A parent raising kids doesn’t have twelve hours; they might have three, broken into pieces. Three focused hours with an agent that holds context, explains, and picks up where you left off is now a real path in. It wasn’t before.

Disabled people. Everyone says “remote work fixed this.” It didn’t. Remote work removed the commute; it did not remove the quiet marginalization — the assumptions made before you speak, the opportunities that evaporate politely. Here’s what’s different now: a disabled person can create in public. Ship a tool. Publish a system. Put working things into the world where the work speaks first, before anyone’s prejudice gets a vote. Shipped software doesn’t disclose anything you don’t want it to. The gate wasn’t just the skill barrier — it was other people. That’s the gate that just cracked.

People with chronic illness. On-call culture, sprint pressure, “always available” — these silently expelled anyone whose energy is real but variable. Building with an agent tolerates working in bursts. The output doesn’t show which hours were good hours.

People far from the industry. No tech scene in your town, no university nearby, no one in your family who’s ever done this work. The agent doesn’t know your postal code.

People priced out of the on-ramp. The degree, the bootcamp, the certifications, the year of free labor to “get experience.” For a large slice of the world that was never a ladder — it was a wall with a ladder painted on it.

People whose English isn’t fluent. The documentation, the forums, the interviews — all in English, always. An agent meets you in your own language and translates the whole field for you in real time. I don’t think people who grew up inside English understand how tall that wall was.

(Each of these groups deserves more than a paragraph, and some of them will get a full article. If you belong to one of them and want to tell me what I got wrong or missed — my inbox is open. That’s not politeness; I need it.)

None of these people were less capable. They were less permitted. Different walls, same gatekeepers — and I was one of them, me and my little contempt for “basic” questions.

Where the wealth goes

So here’s my actual prediction, and it’s not the collapse story and not the utopia story.

The old distribution paid a small number of obsessives 2–3× a good wage, in exchange for their entire lives. I know, because I collected it. The new distribution looks like this: a much wider base of people doing this work well for a decent wage — four solid hours of building, two hours of talking to actual humans like an actual human — and then going to live their lives. The premium doesn’t vanish; it relocates, away from “can endure the grind” toward judgment, accountability, and being the person who knows what correct looks like when the agent’s output is wrong.

History calls this pattern wealth spread, and it never arrived looking like charity — it arrived looking like access. Cheap books spread literacy. The bicycle, around 1900, measurably expanded where women could work and live. The sewing machine collapsed the price of decent clothing. None of these were built to comfort the incumbents. All of them widened the base.

The honest size of the claim

Will this solve poverty? No. And I refuse to pretend otherwise, because overclaiming is how good arguments get dismissed.

But here’s a precedent with numbers attached: when mobile money (M-Pesa) spread through Kenya, researchers publishing in Science estimated that access to it lifted roughly 2% of Kenyan households out of extreme poverty — with the strongest effect for households headed by women. Two percent. A phone-based payment tool. Nobody planned it as an anti-poverty program; it just removed a barrier, and a slice of poverty came off.

That’s the size of claim I’m making. Not salvation — a slice. Another step in a long line of steps: the press, the bicycle, the sewing machine, the phone. Each one moved a slice. Anyone who wants to check any of this — check it. It holds.

Two closing notes

To my fellow guild members: the walls were never the valuable part of you. If your worth was really the scarcity, that was never worth much. If it was the judgment — that travels fine through the open gate.

To you, standing outside — the parent, the person society keeps quietly pushing to the margins, the one who was never permitted: the gate is open. You don’t need my blessing anymore, and you never should have needed it.

One more thing before you step through, because I know what your feed looks like right now. It’s a funeral. “AI is taking the jobs. Tech workers are doomed. More poverty is coming.” Ask yourself whose voice that is. It isn’t yours — you never had the job they’re mourning. The loudest panic comes from the people with the most to lose from an open gate, and fear has always traveled further than invitations on every platform ever built. They’re not describing your future. They’re grieving their scarcity. Scroll past the funeral. It isn’t yours.

The first step costs one sentence:

“Help me learn, and work with me along the way.”

I’m sorry it took us this long to get out of your way.


Where this series goes next

Two articles came out of writing this one, because two questions kept pushing back at me from opposite sides of the gate:

For the newcomer: Your First Month Through the Gate. Concretely, practically — you’ve never written code, nobody in your life does this work, you have three broken hours a day and a cheap agent subscription. What do you build first, what do you ignore, and how do you avoid the traps that were designed for a world that no longer exists? No roadmap-of-forty-courses. One month, one small real thing, shipped.

For the guild: What To Do With Your Hands Now. If the walls were never the valuable part of us, what was? I’ll make the case that the answer is older than our industry — judgment, accountability, and taste — and show what it looks like in practice when your daily work shifts from typing the code to owning the outcome. Including the part nobody wants to hear: which of our hard-won skills genuinely stopped mattering, and which quietly became worth more.

If either of those is your side of the gate, subscribe or check back. And if you’ve already walked through it — tell me what the first month was actually like. I’d rather publish your reality than my guess.

Madalin

Madalin

AI integrator

🚀 Senior Architect | SRE & Database Expert | AI Orchestrator 👋 Building the future at the speed of thought. ⚡️ I don't just write code; I architect high-performance, bulletproof ecosystems. With a foundation in Systems Engineering and a mastery of Go and TypeScript, I bridge the gap between heavy-duty backend reliability and seamless, high-conversion frontends.

Continue the conversation

If this article reflects the challenges your organisation is navigating, explore more practical guidance across Madalin.