# 32 Bits of Authority: On Becoming the Expert I Used to Watch

By AJTheDev — 2025-12-14
Canonical: https://ajthe.dev/blog/posts/32-bits-of-authority.html

---

[← Back to Blog](/blog/)

Thoughts
14 December 2025
6 min read

# 32 Bits of Authority: On Becoming the Expert I Used to Watch

I turned 32. Not a big number, but a definitive one. I finally feel like one of those experts I'd see on TV—the ones who just know their shit without needing to prove it.

![Binary code flowing through a circuit board representing years of accumulated technical knowledge](/assets/images/blog/32-bits-banner.jpg)

I turned 32 recently. It's not a milestone birthday, not really. But something about it
stuck with me. I kept thinking about 32-bit systems, 32-bit processors—the architecture
that defined an era of computing. Four bytes. Enough to address 4 gigabytes of memory.
A limitation that forced creativity. A constraint that demanded efficiency.

And I realised: that's exactly where I am. 32 years of accumulated knowledge,
compressed into a system that finally feels complete enough to run anything I throw at it.

## The Authority of Not Needing to Prove It

When I was younger, I'd watch those tech experts on TV. The ones who'd get asked a
question and just *know*. No hesitation, no caveats, no "well, it depends"
hedging. They'd speak with this quiet certainty that made you trust them immediately.
Not because they were loud or emphatic, but because you could tell—this person has
been through enough iterations to know what actually matters.

I wanted that. Not the TV part, but the *certainty*. The authority that comes
from having seen so many patterns repeat that you can predict the outcome before the
project starts. The ability to look at a complex system and immediately know where
the friction points will be, where the architecture will bend or break, where the
real work actually lives.

I have that now. It snuck up on me.

## Systems Thinking in the Age of AI

Here's the thing about being self-taught for 17+ years: you don't just learn tools,
you learn *connections*. When you have to figure everything out yourself, you
can't afford to silo knowledge. You learn the database because you need to store the
data from the API you built because you needed to feed the frontend you designed because
you had to understand the user's problem. It's all connected because *you* are
the connection.

That's systems thinking. Not knowing one thing deeply, but knowing how a hundred
things interact. Understanding that a "simple" feature request is actually a ripple
that touches the database schema, the API contracts, the frontend state, the user
psychology, and the business logic.

And this—*this*—is the perfect era to have that skill.

AI doesn't replace systems thinking. It **rewards** it. Anyone can get
ChatGPT to write code. But knowing which code to write, how it fits into the broader
architecture, what the second and third order effects will be—that's the skill that
separates someone who prompts AI from someone who directs it. I don't use AI to think
for me. I use AI to execute the systems I already see clearly.

## The Weight of Knowing

There's a weight to real expertise. Not the burden of knowing everything—nobody does.
The weight of knowing *enough*. Enough to be responsible for decisions. Enough
that when a client asks "what should we do?" they're not just looking for an opinion,
they're looking for *your* judgment. Enough that you have to be careful, because
people will trust you and act on what you say.

I feel that weight now. When I tell a client that yes, we can build this, or no, that
approach will fail—they believe me. Not because I'm charismatic (I'm not), but because
I've earned the credibility. I've been wrong enough times in private to be right when
it counts in public.

## 32 Bits

So here I am. 32 bits of addressable memory, filled with 17 years of patterns, failures,
late nights, breakthroughs, and quiet moments of understanding. I finally feel like one
of those experts I used to watch. Not because I'm on TV, but because when I speak about
systems, AI, architecture, or the future of this work—people know I'm not waffling.

The best part? I'm just getting started. 32-bit systems might have their limitations,
but the mind doesn't. And in this era, systems thinking isn't just valuable—it's
becoming the only thing that matters.

Got thoughts? [Hit me up on Discord](https://discord.gg/d39aaZXAjh).
Especially if you're feeling that shift too—the moment you realised you'd become the expert
you once watched.

#thoughts
#career
#systems
#ai

Share this:
[Twitter](https://twitter.com/intent/tweet?url=https://ajthe.dev/blog/posts/32-bits-of-authority.html&text=32%20Bits%20of%20Authority)
[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https://ajthe.dev/blog/posts/32-bits-of-authority.html)

**Written by AJTheDev**

North London developer. AI, FiveM, and web stuff. No bullshit.
