The Race Condition with Reality

A system engineer's view of why the AI era feels so chaotic.

If you spend enough time online, you’ll eventually encounter two very different stories about artificial intelligence.

• AI is about to transform everything.
• AI is dangerous, unreliable, overhyped, and moving too fast.

Both stories contain some truth. Neither fully explains what is happening.

Over the past few years, I’ve become convinced that much of the confusion comes from a simple idea borrowed from computer science: the race condition.

In software, a race condition occurs when multiple processes are running at the same time and the outcome depends on which one gets there first. The term sounds technical, but most of us have experienced something similar.

Imagine a rumor spreading through a high school.

• Students hear it in minutes.
• Teachers hear it later.
• Parents hear about it that evening.
• The principal learns enough to investigate.
• The school board discusses it at the next meeting.

There might not be anyone to blame. Different groups simply operate at different speeds.

Now imagine the rumor is:

• Only partially true.
• Or completely false.
• Or changing as it spreads.

Things get messy. That is what the current AI era feels like to me.

One person tries a chatbot at home and gets a useful answer in seconds. Another person asks a slightly different question and gets something confident but wrong. A student uses AI for homework before the school has a policy. An employee uses it before the company knows what data is safe to paste. A manager hears that everyone should be using AI, while the legal team is still figuring out what that means.

That is not one problem. It is several systems moving at different speeds.

We Are Watching Multiple Races at Once

Many discussions about AI assume there is a single race happening.

Technology advances → Society responds.

Reality is more complicated. Several races are happening simultaneously, and they are all running at different speeds.

Race #1: Capability vs Understanding

AI systems are becoming more capable at an astonishing rate. At the same time, researchers are still learning why some of these capabilities emerge. New behaviors are often discovered after deployment rather than before.

That is why a tool can feel amazing on Monday, confusing on Tuesday, and different again after the next update. The capability is changing faster than ordinary users can build a stable mental model of it.

In previous generations of software, deployment was often close to the finish line.

Build → Test → Launch → Move On

Today, deployment increasingly feels like the beginning of the experiment.

System change → Users adapt → Tools change → Data changes → Expectations change

Organizations that treat deployment as the finish line may discover they have entered a race they didn’t realize they were running.

Race #2: Adoption vs Governance

People can adopt a new AI tool in an afternoon. Organizations often need months or years to develop policies around its use. Governments move more slowly still. This creates a gap.

Employees are already using the technology. Managers are trying to understand it. Compliance teams are drafting guidance. Regulators are debating rules. Everyone is trying to catch up with something that keeps changing.

For example, a worker may paste a customer email into an AI tool because it helps draft a response. The worker is trying to be helpful. The manager may not know it happened. The privacy policy may not mention it yet. The risk may be real even though nobody intended to create one.

This does not necessarily indicate failure. It is evidence that different systems operate at different speeds.

Race #3: Hype vs Reality

Every major technological shift attracts bold predictions.

• Some will prove correct.
• Some will prove wildly optimistic.
• Some will underestimate what is coming.

The challenge is that predictions often travel faster than evidence. A headline can say AI will eliminate a whole category of work before anyone has measured what happens in a messy real workplace. Eventually reality catches up.

The encouraging part is that we are beginning to see more public testing, measurement, and evaluation.

Claims are being challenged and assumptions tested. This is a positive sign that learning is occurring.

Race #4: Innovation vs Resilience

Organizations understandably focus on new capabilities.

• The new capability is exciting.
• The backup plan is not.
• The demonstration gets attention.
• The recovery procedure rarely does.

Historically, this was often manageable because technology moved at human speeds. Today, changes can spread globally before many organizations fully understand what they have adopted.

A demo might show an AI tool answering policy questions perfectly. Six months later, the hard question is not whether the demo worked. It is whether anyone knows what to do when the tool gives a plausible answer from an outdated policy, cites the wrong source, or fails during a busy week.

• Innovation remains important.
• Resilience becomes equally important.

The question is no longer simply: “What can this technology do?”

It is also: “What happens when it fails?”

Race #5: Automation vs Human Adaptation

Technology can change in months. Human systems often change in years. Many aspects (schools, businesses, families) need time to adapt. This has happened before.

A school may need to rethink homework. A business may need to rethink training. A family may need to decide when a child can use a chatbot and how to check the answer. Those adaptations take conversation, practice, and trust. They do not arrive automatically when the software updates.

• The Industrial Revolution created new challenges.
• The automobile created new challenges.
• The internet created new challenges.
• The smartphone created new challenges.
• AI is creating new challenges.

Humans have successfully navigated these transitions before, but rarely by pretending the transition was easy.

Race #6: Scale vs Blast Radius

Both good and bad ideas can spread globally before we fully understand them. The issue is not whether a technology is good or bad. The issue is that scale often arrives before certainty. A mistake that once affected:

• a classroom can now affect significant parts of the education system.
• a company can now affect an industry.

A weak prompt, a bad policy summary, or a copied mistake can move through a whole organization because the output looks polished enough to trust. The better the system is at producing fluent answers, the easier it can be for an error to travel farther before someone notices.

The larger the potential blast radius, the more important monitoring, testing, and learning become.

Why This Feels Different

One reason the AI era feels unusually chaotic is that we have a front-row seat to the learning process, but without much explanation about the process. For contrast, consider rocket launches.

When a rocket explodes during testing, most people do not conclude that physics has failed. They understand that engineers are learning. That understanding didn’t appear overnight.

Society learned to see testing, failure, investigation, and improvement as part of progress. The same happened with aviation and many other technologies. AI may be entering a similar phase.

Researchers publish findings. ↓ Companies revise approaches. ↓ Users discover limitations. ↓ Policies evolve. ↓ Everyone watches.

The process can appear chaotic because we are seeing the troubleshooting rather than only the final result.

The Goal Is Not Perfection

Engineers learn early that complex systems will never be perfect; there will always be issues to address as things change and we learn. The goal is to:

• Identify problems before they become disasters.
• Reduce the blast radius.
• Learn faster than the risks grow.

That mindset may be more useful than either unrestrained optimism or endless pessimism.

The question is not whether AI will create race conditions. It already has.

The question is whether we can identify them, understand them, and respond before they get out of control.

The Good News

The good news is that many people are already doing exactly that.

• Researchers are testing claims.
• Organizations are revising policies.
• Educators are adapting curricula.
• Governments are debating regulations.
• Users are sharing experiences.
• The troubleshooting has begun.

From the outside, that process looks messy. From an engineering perspective, it looks familiar.

The logs are finally coming in. Now we can start figuring out what is actually happening.