In martial arts, belts mean something. A white belt is fresh, humble, still learning how not to fall over. A yellow belt? They’re picking up rhythm. And a third-degree black belt? That’s years of sweat, bruises, humility, and teaching others.

But in software, we sometimes skip the grind. We hand out titles like candy: “You’re a Senior now.” “Congrats, you’re Staff Engineer.” Overnight yellow to third-degree black belt. And that can be more dangerous than it looks.

The Judo Lesson

Judo doesn’t work that way. A black belt takes close to a decade. A third-degree black belt takes even longer, with years of teaching, competing, and embodying Judo’s principles.

Imagine a dojo where someone who can barely tie their belt walks in with three black stripes and starts handing out advice. Everyone would know it’s a farce. Yet in software? Happens all the time.

A Story From the Trenches

I once worked at a company where the newly promoted “principal engineer” left me speechless. During a pull request review, they asked me what a regular expression was. Straight-faced.

This was the same person who had just won a leadership award for lines of code contributed. Not for impact, not for clarity—just raw lines. Dig deeper into the commits, and you could see the trick: introduce a problem, then “heroically” fix it. Line counts soared, dashboards glowed, recognition followed.

I was baffled. Flabbergasted. It felt like standing in a dojo where someone who’s never mastered the basics is swaggering around with a decorated black belt. Everyone sees the mismatch, but the system is wired to reward the illusion.

That moment stuck with me. Because it wasn’t just about one developer. It was about how organizations mistake noise for mastery. And when that happens, the belts stop meaning anything.

The Ego Trap

Fake belts don’t just distort metrics. They warp egos.

• The badge convinces them they are the mastery.

• Admitting “I don’t know” becomes harder.

• They make calls without the wisdom to back them up.

The ego inflates, the mistakes compound, and everyone else pays the bill—especially the leaders who handed out the belt.

The Fast-Paced Industry Problem

Our industry ships fast, breaks faster, and chases hype cycles. That pressure tempts leaders to promote prematurely to look “strong.” But giving a fake belt in this environment is like handing a learner’s permit driver the keys to an F1 car.

Earned, Not Given

• Mastery comes from scars, not dashboards.

• Belts must be earned, not gifted.

• Growth should be real, not cosmetic.

Final Punch

Stop handing out third-degree black belts to yellow belts. You’re not helping anyone—you’re setting them up to fail and dragging yourself down with them.

In Judo, the belt isn’t the prize. The journey is. Software should be the same.

So before you hand out that shiny new belt, ask: have they really earned it? Or are you just skipping steps because it’s convenient?

Because shortcuts in this game cost more than they save.

Once upon a time, software was about hacking something together just to see if it worked. We broke rules. We experimented. We created.

Then the language nerds took over.
The pedantic rule-mongers. The semantic purists who treated curly braces like sacred scripture. They wrapped barbed wire around creativity and called it best practices.

For years, they thrived. They held the keys. They stood at the gates of “proper” development, deciding who was worthy and who wasn’t.

But the tide has turned. AI just detonated their whole playbook.

The End of Pedantry

All their power was in nuance — in being the smartest person in the room about syntax nobody cared about.

Now? AI eats syntax for breakfast. It’ll crank out a working draft faster than you can argue about tabs and spaces. And with that, the gotcha game is over.

So what’s left? Who survives this shift?

The creatives. The builders. The ones who care about finishing, not fussing.

Because here’s the truth: the future doesn’t belong to the guy who can quote the spec. The future belongs to the one who can see something new in their mind and will it into reality — using AI as fuel, not fearing it as fire.

The makers win. The nitpickers lose.

This Is the Manifesto

This isn’t just about code. It’s about energy. It’s about taking back the spirit of what got us here in the first place.

AI doesn’t replace creativity — it removes the shackles that language nerds wrapped around it.

The walls are down. The gatekeepers are irrelevant. And if you’ve got the courage to create, there has never been a better time to be alive.

So here it is, clear and simple:

• Stop asking permission.

• Stop worrying about the “right” way.

• Stop bowing to the rulebooks.

• Pick up the tools. Build. Break. Create. Complete.

History doesn’t remember the pedants. It remembers the rebels.

A Bone for the Purists: How to Survive

But I’ll throw a bone here. If your entire identity has been wrapped up in policing style guides and enforcing “proper” code, you don’t have to vanish. Not yet. There’s a path forward — if you can evolve.

Here’s your survival guide:

• Trade policing for building. Don’t be the human linter anymore. AI owns that job. Start creating things that matter.

• Think in systems, not syntax. Vision > commas. Frame the why and the what, let the machine handle the how.

• Embrace chaos. Creativity is messy. Ride the waves of drafts, iterations, and experiments instead of smirking at imperfections.

• Develop taste. Correctness can be automated. Taste cannot. Learn what resonates with humans.

• Be useful, not right. Nobody cares if you’re correct in theory. People care if you build something that works, something that matters.

The ones who can drop the obsession with being “right” and instead learn to guide, inspire, and create — those are the purists who might just make it through the fire.

Everyone else? The machine has already replaced you.