The Signal Was Never Clean

I learned early that the signal is never clean.

That was true long before AI showed up wearing a nice interface and pretending it invented uncertainty.

I learned it on radios, circuit boards, oscilloscopes, frequency counters, wattmeters, signal generators, and those little alignment tools we called tweakers. You would tune a circuit into spec, sit there for about seven seconds feeling like a genius, then touch another potentiometer and watch the first reading wander off like it had unpaid taxes and a drinking problem.

That was electronics.

Nothing stayed perfect. Everything drifted. Tubes warmed up. Components aged. Connections got flaky. Antennas cared about weather, terrain, grounding, physics, and whatever other little grudges the universe had filed that day.

You did not get truth.

You got readings.

You got evidence.

You got tolerances.

You got a spec window, a meter, a schematic, a test bench, and a system that rarely behaved as politely as the manual suggested it might.

That kind of work changes how you see the world.

It teaches you that “working” and “working correctly” are not the same thing.

It teaches you that confidence is cheap.

It teaches you that a clean-looking output can still be wrong.

It teaches you that systems lie, not always maliciously, but often convincingly.

So when generative AI arrived and half the planet started treating it like a digital oracle with venture funding, I had a slightly different reaction.

I thought: this is fantastic.

I also thought: this is dangerous as hell.

But I never thought it was magic.

To me, AI looks like another noisy system. A powerful one. A strange one. A useful one. But still a system that has to be tuned, constrained, tested, challenged, and judged.

The model gives you signal.

The human still has to know what to do with it.

That is where the story gets interesting.

Before prompts, there were potentiometers

I did not start my career in a strategy meeting.

I started in rural northeast Arkansas, where work was not something people discussed with branding language. Work was work. You did it because it needed doing, because money mattered, because nobody was coming to smooth the road for you, and because the world did not particularly care whether you felt optimized.

I graduated high school at 17. Roughly two months later, I was in basic training at Lackland Air Force Base in San Antonio.

There was not much of a pause.

Part of it was education. Part of it was technical training. Part of it was the simple fact that I did not have rich parents standing by with a checkbook and a thoughtful multi-year development plan. Some people get a runway. Some people get gravel and a shove.

I got ground radio communications.

Air traffic control radio. Long-haul HF. Tactical communications. NATO systems. Big antennas in fields. Radio trailers. Tubes. Patch panels. Test equipment. Systems that had to work because the people depending on them did not need a motivational quote. They needed communications.

For the first six years of my adult life, I lived overseas.

Japan first.

Then Germany.

I met my wife in Japan. We dated there, got married right before leaving, and then moved to Germany for a NATO special duty assignment. We were young, broke, newly married, and living a life much larger than the one I had imagined as a kid in Arkansas.

That changes you.

Japan changed me.

Germany changed me.

The Air Force changed me.

Electronics changed me.

You learn that the world is bigger than your hometown, your assumptions, your accent, your church, your comfort zone, and whatever version of reality you inherited before you were old enough to question it.

You also learn that systems have personalities.

Not technically, maybe. But spend enough nights inside radio rooms, maintenance shops, field sites, and half-documented infrastructure, and tell me machines do not have moods. I will wait.

Some systems fail loudly.

Some fail politely.

Some fail only when the person who understands them is on leave.

Some fail in a way that makes everyone swear the problem cannot exist, which is usually the first sign that it absolutely exists.

In electronics, you learn to isolate faults.

You half-split the problem. Test the midpoint. Move upstream or downstream. Narrow the failure. Stop guessing. Respect the evidence, but never marry the first theory that looks attractive. That is how trouble starts, in troubleshooting and in life.

That mental model followed me into computers.

By the early 1990s, I had become one of those people other people found when a machine would not behave. I could fix things. Not because I was born with mystical diagnostic powers, although that would have saved time, but because radio had already taught me how to think through failure.

Computers were just another signal path with new and creative ways to betray you.

Bad memory.

Bent CPU pins.

IRQ conflicts.

Sound cards stomping on memory ranges.

SCSI termination weirdness.

Config.sys.

Autoexec.bat.

Jumpers.

DIP switches.

Network cards that acted like they had unresolved childhood trauma.

Printers, which were clearly designed by people seeking revenge against civilization.

There was no AI assistant waiting to explain it.

There was no modern web search experience.

There was no polite chatbot saying, “Here are three likely causes,” before confidently inventing a fourth.

You read manuals. You dug through Usenet. You leaned on dial-up BBS communities, technical text files, and other obsessed people who were trying to solve the same ugly problems before the web made everything searchable and somehow still exhausting.

You broke things.

You rebuilt them.

You swapped parts.

You compared notes with other technical weirdos who also thought sleep was more of a suggestion than a requirement.

That was the school.

Not glamorous.

Not always credentialed.

Not always clean.

But useful.

The Amiga in the German flat

My real computer life started in Germany.

My sponsor there, Don, had an Amiga setup. Maybe several Amigas. An Amiga 500, an Amiga 1000, maybe a 2000 later. The exact inventory does not matter as much as the effect it had on me.

I saw that machine and something lit up.

The graphics. The sound. The software. The demos. The whole creative mess of it.

One of the first games I remember seeing was Zoom. I looked at it and thought, holy shit, this is cool.

That was enough.

I had to have one.

This would have been a fine instinct if I had also possessed money, restraint, or the wisdom expected of a newly married adult. Sadly, I had enthusiasm instead, which history shows is often more expensive.

So I went to the base exchange, got credit, and bought an Amiga 500 and a Commodore 1084S monitor. I also bought one of those cheap glue-together fake wood desks, because apparently if you are going to make a financially questionable decision, you should at least give it a command center.

We had almost nothing.

Borrowed furniture.

Bare essentials.

Not much of a mattress.

A small flat in a German village.

A young marriage.

And there I was, proud owner of a computer setup I could not really afford.

My wife was furious.

She was right.

That is an important sentence in any honest marriage: she was right.

But that Amiga opened a door in my head that never closed.

From there, I went deeper.

Building PCs.

Running bulletin boards.

Living on shell accounts before the web became fashionable.

Hanging out on text-based IRC.

Getting into modems, burners, SCSI drives, early servers, Cisco, networking, software collections, and all the early computing chaos that made technology feel less like a consumer product and more like a frontier.

Back then, you did not “onboard” to technology.

You fought your way in.

You learned by breaking things.

You learned by staying up too late.

You learned by reading ugly documentation written by people who clearly hated paragraphs.

You learned by trying something, watching it fail, and then developing just enough suspicion about reality to try again smarter.

That era produced a certain kind of technical person.

Not always polished.

Not always credentialed in the approved institutional format.

Not always easy to manage, a statement I offer with great sympathy to every manager who has ever tried to domesticate a useful technical maniac.

But resourceful.

Curious.

Stubborn.

Able to learn ugly systems from the inside out.

Able to find the fault when the system, the vendor, the log file, and three meetings full of people all insisted the fault was impossible.

That kind of person is not obsolete in the AI era.

That kind of person may be exactly what AI needs.

The long frustration of seeing what you cannot yet build

For most of my career, I have been an infrastructure guy.

Electronics.

Support engineering.

Computer systems.

Endpoint work.

Enterprise platforms.

Program and project work.

Y2K.

Networks.

Servers.

Automation.

Operations.

The kind of work where everything is connected, nothing is simple, and the root cause is usually hiding behind five layers of “that should not happen.”

I loved a lot of it.

I still do.

I still love technology. I still love the home lab. I still love building systems, automations, storage, services, and tools that solve real problems. I still like making the machine do something useful.

But there was always a frustration sitting under the surface.

I had ideas I could not fully execute.

Not little ideas.

Systems.

Products.

Workflows.

Automation models.

Service designs.

Interfaces.

Governance models.

Operating patterns.

I could see them in my head.

That was never the problem.

The problem was getting them out of my head and into the world.

I could explain them to technical people. Some of them got it. I could sketch the architecture. I could describe the business need. I could see the failure modes. I could tell you what the system should do, where it would break, who would resist it, and why the first implementation would probably be wrong.

But I was not a full-stack developer.

I was not a polished designer.

I was not the guy who could sit down alone and turn the entire concept into a beautiful application, an elegant pitch, a clean prototype, a persuasive narrative, and a working implementation path.

I could see the thing.

I could not always build enough of the thing.

That gap is irritating when you live with it for decades.

There is a special kind of pain in seeing the future before you can make anyone else see it. Then, years later, someone else builds something adjacent to what you had in your head and suddenly the market calls it visionary.

You sit there thinking: I saw that.

I knew that should exist.

I just could not drag it out of my skull fast enough.

That is not bitterness.

Not entirely.

Fine, partly.

Let us not ruin the moment by pretending I am a saint.

But mostly it is recognition.

Ideas are not enough.

Taste is not enough.

Technical judgment is not enough.

Being right in your own head is not enough.

At some point, the thing has to become visible. It has to become an artifact. A prototype. A system. A story. A decision. A page. A workflow. A model other people can inspect, challenge, improve, reject, adopt, or build on.

That was the gap.

Then AI started closing it.

AI did not give me ideas. It gave my ideas hands.

AI did not make me creative.

It did not make me technical.

It did not give me decades of troubleshooting scars, radio calibration habits, infrastructure judgment, or a working suspicion of elegant nonsense.

What it did was close the distance between thought and artifact.

That is the whole game.

For most of my career, I could see the thing before I could build it. Now I can build enough of it to find out whether the idea deserves to live.

That is not a small improvement.

That is a career event.

Maybe even a life event.

With AI, I can prototype.

I can code with assistance.

I can shape product concepts.

I can pressure-test architecture.

I can generate interface directions.

I can build pitch narratives.

I can write governance patterns.

I can simulate objections.

I can turn a messy brain dump into a structured article, a working page, a validator, a prompt package, a business case, a runbook, or an implementation blueprint.

Not perfectly.

Not magically.

Not without review.

The machine still gets things wrong. Sometimes confidently. Sometimes beautifully. Sometimes with the kind of smooth wrongness that makes you want to unplug civilization and start over with better documentation.

But it gets me moving.

That matters.

AI changes the distance between thought and action.

For people who already have domain knowledge, judgment, taste, scars, and stubborn curiosity, that distance collapsing is profound. It means ideas that used to sit in the mental parking lot can now become prototypes. It means dormant instincts can become systems. It means imagination can produce evidence.

I am not excited because AI can write a bland email.

The world already had plenty of bland emails. We were not facing a shortage. No civilization has ever collapsed because it lacked more “circling back.”

I am excited because AI lets me turn systems in my head into working artifacts before the energy dies.

That is the difference.

That is the ignition.

The model is not the differentiator

Here is the part people keep missing.

The model is not the differentiator.

Access is not competence.

A prompt box is not a strategy.

A subscription is not a capability.

Everyone can open the same model, more or less. Everyone can type into it. Everyone can ask for a plan, a script, a summary, a pitch, a design, a workflow, or a miracle with bullet points.

The results are wildly different.

That should tell us something.

AI amplifies the person using it.

It amplifies clear thinking.

It amplifies domain knowledge.

It amplifies good taste.

It amplifies structured reasoning.

It amplifies strong questions.

It amplifies the ability to evaluate output against reality.

It also amplifies laziness, nonsense, shallow strategy, cargo-cult leadership, fake expertise, and executive theater at machine speed.

That last part is going to be expensive.

Some people use AI like a calculator.

Some use it like a search engine with confidence issues.

Some use it like a ghostwriter.

Some use it like a junior analyst.

Some use it like a design partner.

Some use it like an engineering assistant.

Some use it like a mirror.

Some use it like a slot machine for corporate vocabulary, which should probably require licensing.

The tool is powerful.

The operator still matters.

If you spent years troubleshooting systems where a wrong assumption could waste hours, break production, or leave people stranded in the middle of a problem nobody wanted to own, AI feels familiar in a strange way.

You learn to ask:

What did it miss?

What hidden dependency did I fail to state?

What constraint did I assume but never told it?

What source is it leaning on?

What sounds too confident?

What would prove this wrong?

What happens if this goes into production and the adult supervision leaves the room?

That is not just prompt engineering.

That is engineering judgment.

Do not rule out the old hats

This is where I think companies need to be very careful.

There is a lazy assumption floating around that the AI future belongs to the youngest people in the room because they grew up closest to the newest tools.

Sometimes that will be true.

Plenty of younger workers are fast, creative, fearless, and technically sharp. I am not here to turn this into a generational cage match. The internet has enough nonsense already, and most of it has comments enabled.

But age is not the variable that matters most.

Learning velocity matters.

Judgment matters.

Domain depth matters.

Curiosity matters.

Pattern recognition matters.

Operational scar tissue matters.

The ability to work inside ambiguity matters.

The ability to know when a system is producing polished garbage matters more than people want to admit.

That is why I would not rule out the old hats.

Some of us have been working with probabilistic systems, tolerances, noisy signals, operational constraints, brittle infrastructure, incomplete documentation, and high-consequence environments for decades.

We may not describe it with trendy vocabulary.

We may not call ourselves “AI native,” mostly because some of us still have a small shred of dignity left.

But the mental model is there.

The question is whether the experience keeps learning or calcifies.

Because there are two very different late-career paths in the AI era.

One path is defensive.

The work changes. The tools change. The language changes. The experienced person retreats into resentment. Everything new is stupid. Everyone younger is naive. Every tool is a toy. Every change is theater. That path is real, and it will not end well.

The other path is leverage.

The experienced person keeps learning. The new tools meet old judgment. Decades of tacit knowledge suddenly become more executable than they have ever been.

That second path is the one I care about.

The risk is real. Boston College’s Center for Retirement Research published a June 30, 2026 brief finding that workers age 55 and older are just as exposed to AI as mid-career workers, and that workers in high-AI-exposure jobs have seen a rise in job exits since the surge in generative AI use. That is not a cute trend. That is a warning flare.

AARP’s updated 2026 research shows the same tension from another angle: older workers continue to see AI as both an opportunity and a threat, with concern outweighing optimism.

So no, I am not pretending this is all inspiration and sunrise photos.

AI can push people out.

AI can expose skill gaps.

AI can become another excuse for lazy age bias wrapped in innovation language.

But that is only half the story.

The other half is leverage.

The people who understand the business, the risks, the exceptions, the data, the customers, the systems, the politics, the buried operational debt, and the real cost of failure are not optional in serious AI work.

They are the difference between a demo and a capability.

A demo has to impress people for ten minutes.

A capability has to survive reality.

Those are different sports.

Retirement got interrupted

Before AI pulled me back into the deep end, I had started thinking more seriously about retirement.

Not because I hated the work.

Not because I had nothing left to contribute.

Not because I was done.

I was bored.

That is the honest answer.

Infrastructure work matters. Support engineering matters. Enterprise platforms matter. Keeping real systems alive matters. But after enough years, you start doing the math.

Sixty-two?

Sixty-five?

Sixty-seven?

You start thinking about the glide path. You start wondering when it makes sense to hang it up from corporate America. You look around and ask whether the next version of work is going to feed the same part of you that got lit up by radios, Amigas, networks, servers, and all the strange machinery that carried you this far.

For me, the answer was starting to look uncertain.

Then AI changed the equation.

Not because it was shiny.

Shiny wears off.

AI got my attention because it made old ideas newly reachable.

It turned the work from maintenance mode back into invention mode.

It gave me a way to combine infrastructure, architecture, automation, product thinking, design, writing, governance, and problem-solving into one operating surface.

That is why I can spend absurd hours on this and not experience it as normal work.

Yes, that probably sounds unhealthy.

Some of it probably is.

Obsession rarely shows up wearing a balanced lifestyle and a sleep tracker.

But there is also something deeply energizing about discovering, late in a career, that the thing you have been preparing for may not be behind you.

It may still be ahead.

That surprised me.

I thought AI might help me finish the race more efficiently.

Instead, it made me wonder whether I was done racing at all.

Experience still has to earn the room

I do not want to romanticize experience.

Experience can be powerful.

It can also become a museum exhibit with opinions.

Years alone do not make someone valuable.

Scars alone do not make someone wise.

Seniority alone does not equal judgment.

We have all met people with twenty years of experience who really had one year of experience repeated twenty times, usually with a larger calendar and stronger coffee.

Experience only matters if it keeps metabolizing new reality.

That is the standard.

If AI is changing the work, experienced people have to change with it.

Not by pretending to be twenty-five.

Not by chasing every tool.

Not by posting synthetic enthusiasm on LinkedIn and calling it transformation.

By doing the work.

Learn the tools.

Build real things.

Understand the failure modes.

Study the governance issues.

Know where the data comes from.

Know what should not be automated.

Know what must remain human.

Know what can be accelerated safely.

Know when the model is helping.

Know when it is just producing expensive fog.

That last one may become one of the most important skills in the enterprise.

Because the surface is getting easier.

The danger is getting quieter.

The output looks better.

The reasoning may not be.

That is a dangerous combination.

The Federal Reserve noted in April 2026 that Census Bureau business survey data showed about 18 percent of firms had adopted AI by the end of 2025. The tool adoption is moving, but institutional maturity is still uneven.

That matches what I see.

People are experimenting faster than organizations are adapting.

The toy phase is easy.

The governance phase is harder.

The production phase is where the bodies are buried.

That is where experienced operators matter.

This is not young versus old

The age framing has to be handled carefully.

This is not young versus old.

That is lazy.

The World Economic Forum reported in June 2026 that more than one in three young workers globally are in occupations with medium to high exposure to AI-driven task change. So early-career workers are being hit too. The ladder is moving under them before some even get a proper first rung.

That matters.

If AI eats too much entry-level work, companies may eventually discover that senior people do not hatch fully formed from quarterly planning decks. Someone has to learn the basics. Someone has to make mistakes. Someone has to do the junior work long enough to become the person who can handle the senior work.

Apparently this needs saying because civilization has a habit of removing the bridge and then acting surprised when nobody can cross the river.

So the real divide is not young versus old.

It is adaptive versus static.

Curious versus performative.

Disciplined versus careless.

Builder versus passenger.

Some young workers will be extraordinary with AI.

Some will become prompt-dependent and shallow.

Some older workers will be pushed aside unfairly.

Some will refuse to move.

Some will become more valuable than ever because they know things the model does not know, and they know how to make the model useful without trusting it blindly.

That is the interesting part.

AI does not erase experience.

It exposes the quality of it.

A life measured in signals

I have spent a long time around technology.

From rural Arkansas to the Air Force.

From Japan to Germany to California.

From radios to computers.

From oscilloscopes to Amigas.

From bulletin boards to enterprise infrastructure.

From config.sys to cloud.

From half-split troubleshooting to AI agents.

It has been a strange arc.

A good one.

Not always easy. Not always elegant. Sometimes expensive in ways my wife would still be fully justified in mentioning.

But it has been mine.

And now, after all these years, I feel oddly early again.

That is the part I did not expect.

AI has made me feel something close to what I felt when I first saw that Amiga in Germany.

Curious.

Restless.

Slightly unreasonable.

Convinced something important is happening and unwilling to sit politely on the sidelines while other people define it badly.

Maybe some of these thoughts will age well.

Maybe some will not.

That is fine.

Every signal exists in time.

Every reading has context.

Every system changes.

You tune as best you can with the instruments you have, then you test again.

But here is what I believe right now.

The future of AI will not belong simply to the people with the newest tools, the youngest resumes, the loudest opinions, or the cleanest personal brand.

It will belong to the people who can think clearly under uncertainty.

It will belong to the people who can combine imagination with discipline.

It will belong to the people who know that a beautiful output can still be wrong.

It will belong to the people who can keep learning without surrendering judgment.

And some of those people are old hats.

Do not rule them out.

Some of us have been tuning noisy systems our whole lives.

AI did not give my ideas life.

It gave them hands.