The Case for Anti-Gatekeeping
The single most human thing we do is teach each other. Gatekeeping knowledge isn't protecting standards — it's betraying the species.
A job listing crossed my feed last week. Entry-level developer role. Required: a four-year computer science degree. Also required: three years of professional experience. For an entry-level position. The listing had been up for sixty days.
Meanwhile, somewhere, a self-taught developer with a portfolio of shipped projects, an open-source contribution history, and genuine curiosity about the craft didn't bother applying. The gate said "not for you." The gate was wrong.
This post isn't a plea for inclusion. It's an argument that gatekeeping is fundamentally stupid — that it works against the mechanism that built everything we have.
Knowledge Transfer Is What Makes Us Human
This isn't metaphorical. The ability to accumulate and transmit knowledge across generations — culture, language, technique, science — is the defining characteristic of our species. Most other animals start from scratch each generation. We don't. A chef today stands on thousands of years of culinary technique. A developer stands on seventy years of computer science. Neither invented their craft. Both inherited it through the single most powerful technology humans have ever developed: teaching.
Hoarding knowledge — whether behind degrees, credentials, paywalls, or in-group jargon — works against this mechanism. It doesn't protect standards. It slows the engine that created those standards in the first place.
The kitchen taught me this early. The best chefs teach. They share techniques freely, train their staff aggressively, and measure their legacy by who they mentored, not what they hoarded. I myself have mentored multiple young cooks who have grown into successful chefs, now mentoring their own cooks. The chefs who hide recipes, refuse to explain their methods, and guard their stations like territory? Their techniques die with them. Every great culinary tradition survives because someone wrote it down and handed it to the next cook.
What Gatekeeping Looks Like in Tech
Credential gates. Degree requirements for roles that don't need them. A CS degree tells you someone completed a curriculum. It doesn't tell you they can build something, debug it, ship it, and maintain it. Filtering for credentials instead of capability is the laziest possible screening method.
Purity tests. "You're not a real developer if..." If you use AI. If you're self-taught. If you learned JavaScript first instead of C. If you can't invert a binary tree on a whiteboard. These tests don't measure engineering ability. They measure proximity to a specific educational and cultural path.
Hostile communities. Open source projects where "read the docs" is a weapon instead of a welcome. Forums where asking a beginner question gets you condescension instead of help. The irony: these communities exist because someone shared knowledge freely. The hostility betrays their own origin.
Interview theater. Algorithmic puzzles for frontend roles. System design questions for junior positions. Whiteboard exercises that test memorization and performance anxiety, not the ability to build software in a real environment with real tools.
Economic gates. The quiet ones. Unpaid internships. Bootcamp tuition. The assumption that everyone can afford to stop earning for six months to learn full-time. These gates don't filter for talent. They filter for financial privilege.
The Arguments Against (And Why They're Wrong)
"Standards matter." Yes, they do. But standards should measure what you can do, not where you learned to do it. A chef doesn't check your culinary school diploma. They taste your food. A good hiring process doesn't ask where you studied. It looks at what you've built, how you think, and how you handle a problem you haven't seen before.
"CS fundamentals are important." Some are, for some roles. But "important to know" and "required to enter" are different things. You can learn fundamentals on the job, through projects, through mentorship. You can't learn work ethic, systems thinking, or genuine curiosity from a textbook. Those come from experience — and they come from all kinds of experience, not just the kind that happens in a computer science department.
"We need to filter somehow." Yes. Filter on output, not input. Show me what you've built. Show me how you think about a problem. Show me how you respond when something breaks. A portfolio of shipped projects tells me more about a developer than any credential.
"AI makes it worse — anyone can generate code now." This is the gatekeeping instinct in real time. A new tool democratizes access, and the first reaction is to raise the walls. The correct reaction is to raise the bar for what "good" means — to value judgment, architecture, taste, and systems thinking over raw syntax production. If the only thing separating you from a beginner is that you memorized more syntax, AI isn't the threat. Your skill set is.
Anti-Gatekeeping as a Professional Philosophy
Anti-gatekeeping isn't just a belief I hold. It's a practice. It shapes how I hire, how I build, how I share, and what I refuse to tolerate.
Open knowledge sharing is a non-negotiable. When I evaluate a company or a team, the first thing I look for is how information flows. A culture that silos knowledge, discourages questions, or hoards expertise behind seniority walls is a fundamental mismatch. I've walked away from environments like that, and I'd do it again. The moment "that's not your job to know" enters the vocabulary, the organization has started dying.
Hiring based on potential, not credentials. Fifteen years of building teams in hospitality taught me how to evaluate people. My approach: word-of-mouth recruiting, paid stages with immersive onboarding, and evaluation based on adaptability and attitude under full support. Give people the tools, the training, and the opportunity. Then see what they do with it. The person with no formal background who learns fast and shows up with genuine curiosity will outperform the credentialed candidate who's just checking boxes — every time, in every industry I've worked in.
Default to open. The Dev Context Methodology is open source. The plugin ecosystem is open source. These blog posts describe my process transparently, including the mistakes. Not because openness is virtuous — because it's effective. If someone takes DCM and builds something better, that's a win. The methodology is more valuable shared than hoarded. The rising tide raises all boats, and I'd rather be in a harbor full of boats than alone with a bigger one.
"Offhanded excellence." This is a term from my professional philosophy — user-friendly, approachable, never gatekeeping, supporting those around you, giving back to the communities you learn from. Excellence that doesn't need to announce or protect itself. It shares freely because sharing doesn't diminish it.
Community as the point, not the perk. The long-term vision I'm building toward is a cross-discipline network of creatives, business leaders, academics, organizers, professionals, and developers working toward systems of efficient mutual benefit. Gatekeeping is the antithesis of this vision. You can't build a community by deciding who doesn't belong. You build it by making the door wider and the work better.
The Personal Angle
I'm writing this as someone who would be gatekept out of most tech roles on paper. No computer science degree. No bootcamp certificate. Fifteen years in kitchens and on job sites. Self-taught over fourteen months with AI as a development partner.
The work tells a different story. Public repositories across multiple languages. A project lifecycle methodology published as a Claude Code plugin. A Tauri desktop app with a Rust backend. A 3D knowledge graph for Obsidian built with Three.js. A text-to-speech system that required debugging Unix process groups and Python file descriptor inheritance. This portfolio site, this blog, and open-source plugin marketplaces.
The gate doesn't measure what it claims to measure. It measures access, not ability. It measures where you've been, not what you can do.
AI is the great equalizer here. It gives anyone with curiosity and discipline access to the same capabilities that used to require years of formal education. That's not a threat to quality — it's an expansion of who gets to participate. And the instinct to restrict the tool rather than raise the standard is the same gatekeeping impulse that's been wrong in every era. There's no longer a need to fight over slices when we can work to make the pie bigger.
Every generation of gatekeepers has been on the wrong side of history. The medieval scriptoria that restricted literacy to monks. The trade guilds that limited craft knowledge to guild members. The universities that charged fortunes for information that wanted to be free. Tech's version isn't different — it's just newer.
Share what you know. Teach who asks. Hire for what people can do, not where they learned to do it. Build the door wider, not the wall higher.
The best thing about knowledge is that giving it away doesn't make you have less of it.