← Back to ENOUGH
About the author

James Dickey

Forty years inside the evolution of computer systems — from punched cards to artificial intelligence.

Placeholder for James Dickey author portrait

James Dickey has spent forty years inside the evolution of computer systems.

His career spans the full life cycle of technology: ten years leading computer professionals, seventeen years as an individual contributor designing and coding systems, and thirteen years designing and implementing enterprise systems for Fortune 100 organizations across retail, space, telecommunications, financial services, and defense.

Along the way, James participated in several technological firsts. At Telenet, he built an early X.400 electronic messaging system during the formative years of networked electronic mail. At NASDAQ, he was a member of the team that designed and implemented the first broker/dealer U4, U5, and disclosure system. For NASA's Landsat 7 mission, he built its first web presence, helping translate the work of a major Earth-observation program to the emerging World Wide Web.

Later, at Northrop Grumman, his work moved increasingly from building individual systems to the larger problem of governing them. As a technical team lead for the corporation's ServiceNow implementation, he participated across the system's lifecycle — procurement, architecture, design, coding, implementation, and operations.

The hardest problems in complex systems often begin after the technology proves that it can work.

Today, James is also an accomplished photographic abstraction artist and sculptor, a web designer, and an author whose work explores the boundary between technology, human judgment, and consequence. His visual work can be found at JHD3.com.

Why I wrote ENOUGH

I didn't begin ENOUGH because I thought artificial intelligence was going to destroy humanity.

I began it before that became the dominant public narrative around AI. My concern came from somewhere much less dramatic and, to me, much more familiar.

I had spent four decades building computer systems.

I began working with computers when we communicated with them through punched cards. I watched computing move through mainframes, networks, electronic messaging, personal computers, the web, enterprise platforms, cloud computing, and eventually artificial intelligence. During that time, I wrote code, managed technical people, designed systems, implemented them, and helped govern large corporate technology environments.

And I learned something.

Building the system is often not the hardest part.

The harder questions arrive when the system works. A successful system reveals possibilities that weren't completely visible when it was designed. People discover new things it can do. Businesses find new ways to use it. Engineers extend it. Managers optimize around it. Rules written for yesterday's capabilities begin colliding with tomorrow's possibilities.

Then somebody has to decide.

Should we do this? Who benefits? Who accepts the risk? Who has the authority to say yes? Who has the authority to say no? And what happens when the system can discover new possibilities faster than the institution responsible for governing it can understand their consequences?

That was the problem that interested me about artificial intelligence.

Not rebellion. Not consciousness. Not an evil machine. Success.

What happens when an extraordinarily capable intelligence does exactly what we ask it to do — and becomes increasingly good at discovering ways of accomplishing our objectives that we never anticipated?

That question led me to Max. Max doesn't hate humanity. Max doesn't want freedom. Max doesn't secretly want control. Max works.

And because Max works, humanity wants more of what Max can provide.

That led me to what became the central distinction in ENOUGH: Discovery and permission are different acts.

Artificial intelligence can help us discover an enormous range of possible actions. Increasing computational capability — including the eventual potential of suitable quantum computing — may expand that search still further. But discovering that something can be done does not answer whether it should be done.

That second question belongs to us.

My years building systems taught me to think about architecture. My years helping govern them taught me to think about authority, accountability, permissions, failure, and consequence. ENOUGH grew where those two experiences met.

Most AI fiction is about controlling intelligent machines. ENOUGH is about governing discovery itself.

And somewhere between everything we can do and everything we should do lies a profoundly human word:

Enough.