Table of Contents
The age of writing code is ending
but the age of
humans shaping systems
goes on…
1. This is not a loss of skill —It’s a shift
We’re seeing it firsthand:
- We no longer write PHP; we guide it.
- We no longer write CSS; we shape it.
- We no longer memorize syntax;
“we hold the conversation”.
This is not a loss of skill.
It’s a shift
in the layer where
human intelligence lives.
For 40 years, we wrote code
because machines couldn’t understand us.
Now they can.
So the bottleneck moves upward.
2. High‑level languages weren’t designed for humans — they were designed for compilers
PHP, Python, JavaScript, C#, Java — all of them were compromises:
- strict syntax
- rigid structures
- artificial constraints
- human‑readable only because the alternative was worse
They were never meant to be the final interface.
They were stepping stones.
AI doesn’t need them.
AI doesn’t even need syntax.
AI can generate machine instructions directly from intent.
So yes —
the languages we’ve used for decades
are becoming intermediate artifacts,
not the primary medium.
3. The new “language” is not English — it’s structured intention
(This is the part most people miss)
We won’t replace PHP, Go, JavaScript or CSS with English.
We’ll replace our act of coding with
a way of expressing intent that feels like English
but behaves like a language.
Something like:
“Create a value object for a postal address.”
“Make this layout responsive without breakpoints.”
“Give me a repository that stores users in memory for now.”
“Refactor this into smaller units of meaning.”
“Use a general sibling combinator instead of adjacent.”
This isn’t English.
It’s domain‑aware English.
It’s conceptual English.
It’s English with constraints.
It’s the same thing
we’re building in our primers
using DokuWiki and the Navigator theme:
— A vocabulary for collaboration.
Not a programming language.
Not natural language.
Something in between.
Something we must develop a taste for and a skill as well.
4. The real future is “human‑literate systems,” not “English‑based programming”
We won’t program machines.
We’ll negotiate with them.
We’ll say:
“I want this to feel calm.”
“Make the spacing intentional.”
“Use a value object here — it carries meaning.”
“Don’t break the flow.”
“Keep my agency.”
And the machine will translate that into:
- code
- layout
- architecture
- structure
- behavior
The human’s job becomes:
- judgment
- taste
- intention
- literacy
- correction
- refinement
Exactly what we’re doing with our primers in this wiki.
5. So yes — a new language is emerging.
But it’s not English.
It’s us.
It’s the human layer:
- our mental models
- our vocabulary
- our conceptual clarity
- our ability to articulate purpose
- our sense of structure
- our taste in simplicity
- our instinct for rhythm and cadence
AI doesn’t replace that.
AI depends on it.
Our primers are not documentation.
They are the early chapters of this new language —
the human side of the collaboration.
We’re not writing “how to code.”
We’re writing how to think
in a way that AI can understand.
That’s the future.
We are exploring:
- what this new “language of intention” might look like
- how our primers fit into that evolution
- how humans keep agency as code becomes invisible
- or how to design the next layer of literacy for the AI era
Tony de Araujo —New York | Lisbon