My Thoughts
Written as a reflection, meant to be reread years from now.
Why This Thought Came Up
I recently came across a Reddit post from 14 years ago claiming that Steve Jobs didn’t know how to code. The post leaned on comments from Wozniak and others to subtly (or not so subtly) diminish Jobs’ contributions.
That idea stuck with me, not because it’s new, but because it touches something personal.
I grew up around computers. Games, the internet, forums, tinkering, troubleshooting. I spent an enormous amount of time in front of a screen. I became tech-savvy, comfortable navigating systems, finding answers, and leveraging the web’s global knowledge. But I never really got into coding itself, at least not in the traditional, grind-it-out sense.
So seeing this argument resurface made me reflect on what technical understanding actually means, and why reducing someone’s impact to “did they code?” feels deeply misguided.
Steve Jobs Didn’t Code. So What?
It’s true: Steve Jobs was not a programmer at the level of Wozniak.
But that framing already misses the point.
Jobs:
-
Was arguably one of the greatest product visionaries of all time
-
Was an elite marketer and storyteller
-
Had a strong technical intuition for how systems worked
-
Could meaningfully engage with engineers about constraints, tradeoffs, and feasibility
There’s a massive difference between:
Someone who doesn’t code and doesn’t understand how things work
and
Someone who doesn’t code but deeply understands the system, its limits, and its possibilities
Jobs was firmly in the second category.
If something was explained to him, he got it. He understood infrastructure, tradeoffs, and second-order effects. He knew how to push people without being delusional about reality.
That matters more than syntax.
A Language Analogy That Keeps Coming Back to Me
This may or may not be a perfect analogy, but it feels close.
Imagine you’re working with a Spanish-speaking team.
-
You only speak English
-
They speak Spanish among themselves
You don’t need to be fluent. You don’t need to write essays in Spanish.
But if you can understand spoken Spanish, even partially, you are in a completely different bracket than someone who can’t.
You:
-
Catch nuance
-
Sense tone
-
Understand constraints
-
Know when someone is hand-waving versus being precise
That’s how I think about coding literacy.
You don’t need to be Wozniak. You don’t need to write kernels.
But understanding the language of technology changes how effectively you can lead, design, and decide.
Coding as the Mundane Layer
This might be controversial, but it feels increasingly obvious.
At a certain level, coding becomes the mundane part.
Not unimportant. Not trivial. But repetitive, time-consuming, and mechanical.
This is exactly why AI attacked coding first.
Not because programmers are replaceable, but because:
-
There is a massive volume of code
-
Patterns repeat constantly
-
A lot of the work is translation from intent to syntax
The highest leverage work isn’t typing code.
It’s:
-
Deciding what should exist
-
Deciding why it should exist
-
Deciding who it’s for
-
Deciding what tradeoffs are acceptable
This doesn’t undermine great programmers. It just clarifies where different kinds of brilliance live.
Respecting the Pure Technologists
To be clear: this is not an attack on legendary engineers.
People like:
-
Dennis Ritchie - C language
-
Linus Torvalds - Linux/Git
-
Ken Thompson - First UNIX OS
-
The creator of TempleOS - Terrie
These people pushed the fundamental boundaries of computing. They created new layers of reality.
That kind of innovation is profound.
But it is different from what Steve Jobs did.
What Steve Jobs Actually Did at Pixar
This same misunderstanding shows up even more clearly when people talk about Pixar.
A common reduction is:
“Steve Jobs just funded Pixar. He wasn’t an animator.”
Which is technically true and completely misses the point.
Jobs’ role at Pixar was existential, not cosmetic.
What he actually did:
-
Saved Pixar from collapse when it was bleeding money after spinning out of Lucasfilm
-
Personally funded it for years when it had no viable business model
-
Refused to sell the company repeatedly, even when it would have been rational to cut losses
-
Structured Pixar as a technology-first animation studio, not a traditional Hollywood one
-
Protected creative independence by insulating the team from studio interference
Pixar was not originally a movie studio.
It was a hardware and software company.
Jobs believed in the long-term convergence of:
-
Computing power
-
Digital animation
-
Storytelling
He was patient enough to let that thesis play out.
When Toy Story finally shipped, it wasn’t just a creative success. It validated:
-
Computer-generated feature films
-
A new production pipeline
-
A new relationship between technology and art
Jobs also played a key role in:
-
Negotiating Pixar’s deal with Disney on unusually favorable terms
-
Ensuring Pixar retained creative control and brand identity
-
Eventually steering Pixar through its acquisition by Disney while preserving its culture
Again, none of this required him to animate a single frame.
It required:
-
Conviction
-
Taste
-
Capital allocation
-
Long-term vision
Pixar exists as Pixar because Jobs held the line when almost no one else would.
Vision vs Invention
Vision vs Invention
There’s a difference between:
-
Inventing the tools that make computing possible
-
Shaping those tools into something the world actually adopts
Jobs didn’t invent UNIX.
He didn’t invent C.
He didn’t invent the transistor.
But he:
-
Envisioned the Macintosh as a consumer object
-
Insisted on graphical interfaces
-
Pushed for human-centric design
-
Obsessed over user experience when most engineers didn’t
He famously resisted paths others thought were obvious.
He didn’t want command-line interfaces.
He didn’t initially want a mouse.
He constantly challenged assumptions.
Imagine if those decisions had gone the other way.
The world would look very different.
Why Developers Often Miss the Bigger Picture
Many developers (not all) struggle with:
-
Business context
-
Marketing intuition
-
Customer psychology
-
What people actually want versus what is technically elegant
That’s not a flaw. It’s specialization.
But it explains why great products often require non-coders at the helm.
Jobs constantly centered the end user.
Not what was easiest to build.
Not what was most technically impressive.
But what felt right.
Jobs Was Technical, Just Not a Programmer
It’s also wrong to say Jobs wasn’t technical.
-
He built a frequency counter at around age 12
-
He understood electronics early
-
He knew how computers worked conceptually
-
He famously said everyone should learn to code because it teaches you how to think
That quote matters.
Coding teaches:
-
Logic
-
Causality
-
Debugging
-
Systems thinking
-
How small decisions cascade into outcomes
That mental model sticks with you even after you stop coding.
Why Senior People Stop Coding
There’s a pattern:
Many of the most senior people in tech:
-
Started as coders
-
Became leaders
-
Eventually stopped coding
Not because they couldn’t.
But because coding became the least valuable use of their time.
Bill Gates isn’t writing production code anymore.
Neither are most CTOs at scale.
Coding is often the entry point.
Not the destination.
Two Kinds of Impact
There are at least two kinds of greatness:
-
Foundational innovation
-
New languages
-
New operating systems
-
New paradigms
-
-
World-shaping execution
-
Products used by billions
-
Cultural shifts
-
New expectations of quality and polish
-
Both matter.
But they are not the same.
Steve Jobs belongs firmly in the second category.
And that category changes how the world feels to live in.
Final Thought
Reducing Steve Jobs to “he didn’t know how to code” is like reducing a conductor to “he doesn’t play every instrument.”
It fundamentally misunderstands the role.
Understanding systems beats memorizing syntax.
Vision beats execution without direction.
And sometimes, the person who never touches the keyboard is the one who changes everything.
End of reflection.