Computational Thinking Was Always the Point

For a long time, the argument has been that everyone should learn to code. Not to become software engineers, but because coding teaches you how to think — how to break things down, see systems, be precise, be discrete.

That argument was right. It was just aimed at the wrong output.

The skill was never about code. It was about thinking. It was always about thinking. And now that AI is rewriting what it means to build software, that thinking skill matters more than ever.

What is Computational Thinking?

Computational thinking is a set of mental habits — decomposition (breaking big problems into small ones), pattern recognition (this looks like something I've solved before), abstraction (what matters here and what doesn't), and algorithmic thinking (what steps reliably get me to the result).

None of that requires a computer. None of it requires Python or JavaScript. These are cognitive skills, and they transfer everywhere.

The engineers who thrived weren't the ones who memorized syntax. They were the ones who knew how to think about problems.

From Code to Intent

The thing that's actually changing is the interface between what you think and what the machine does.

For a long time, that interface was code. You learned the machine's language. One wrong character and everything broke. No ambiguity allowed.

That's disappearing. Now you describe what you want. The AI fills in context, makes inferences, produces something close to what you had in mind.

The new programming language is English. The new compiler is context. And the new debugger is taste — knowing good output from bad in the context of the problem you're actually solving.

But you still have to know what you want. You still need to decompose a goal into sub-tasks, recognize patterns, think through edge cases, and judge whether the output actually solves your problem. Those are computational thinking skills. They were required for good code. They're equally required for good prompts and good AI workflows.

What This Means for Learners

If you're a student figuring out what skills matter in an AI world, start here. Learn to think in systems. Learn to decompose. Learn to ask precise questions and spot what's wrong when something misses.

That practice doesn't have to be programming. Logic puzzles, structured writing, data analysis, design thinking, philosophy, math, game design — anything that rewards precise thinking works.

But don't abandon coding either. Writing code is still one of the best ways to build the computational thinking muscle. The machine's feedback loop forces a precision that few other activities match. You don't code because AI needs you to — you code because it teaches you to think in ways that transfer directly to directing AI.

You don't need to become a programmer. But the habits of mind that make a great programmer will make you extraordinary at working with AI.

What This Means for Educators

For those that work in education — they've watched curricula chase technology for decades — this is actually an opportunity, not a crisis.

The case for teaching computational thinking never depended on "your students will get coding jobs." It was always about thinking skills that help people navigate complex systems and solve unfamiliar problems. That case just got stronger.

The framing shifts. We're no longer teaching computational thinking as a prerequisite for programming. We're teaching it as a prerequisite for working with AI. The destination changed. The route is the same.

Students who develop these habits won't be replaced by AI. They'll be the ones who know how to use it.

Full Circle

I know this because I lived it.

In 2017, as Chief Innovation Officer at Mid-Pacific Institute, I helped write the school's technology vision. It opened with something that felt ambitious at the time.

Mid-Pacific is future oriented, anticipating a landscape that does not yet exist. Within our curriculum, we believe that technology is not a discrete field of learning unto itself. Rather, technology is one of many "languages" students learn to use in their lives as they grow. While remaining flexible and responsive to rapid changes in the field of technology, we empower our students with technical experience and knowledge necessary to be relevant in the age of tomorrow.

This was nine years ago. Before GPTs were mainstream. Before agents. Before prompt engineering was even a thing. The section on computational thinking went further.

At Mid-Pacific we do not teach students a specific computer programming language nor a set of developer tools. Rather than focus on coding as a skill, we aspire to teach computational thinking so that this model of thinking and problem solving can be applied throughout our student's lives in myriad situations. Our students will be computer programming language agnostic and possess the ability to quickly learn any new computer programming languages because they can think programmatically.

The vision listed six characteristics of computational thinking — analyzing and organizing data, modeling abstractions, formulating problems for computers to assist with, identifying and testing solutions, automating via algorithmic thinking, and generalizing to new problems.

The "programming language" our students need now isn't Python — it's English, spoken with precision. The "myriad situations" aren't hypothetical. The landscape that didn't exist yet? It's here.

We didn't predict AI. We predicted the tools wouldn't matter. What would endure was the thinking. That turned out to be right.

The Long View

Every big shift in computing looked like a threat from the outside. Assemblers replaced machine code. High-level languages replaced assemblers. Frameworks replaced raw libraries. Each time, people worried the abstraction would make the underlying knowledge irrelevant. Each time, the people who understood what was happening underneath built more powerful things.

AI is the next abstraction. But the people who'll do the most with it aren't treating it as a magic box — they know how to structure a problem, communicate intent, evaluate output, and iterate.

That's computational thinking. It was the skill for writing good code. It's the skill for building well with AI. And it'll stay relevant through whatever comes next.

AI will do more and more of the building. The thinking about what to build, why to build it, and whether it worked — that stays human.

The skill doesn't get old. It just finds new places to live.

---