The machines learned our language. Not our meaning.
For 180 years, making software meant learning the machine's language. Punched cards, then assembly, then C, then Python — each one friendlier than the last, and each one still years of study before you could build anything a stranger would use.
That barrier fell. You can now describe an app in ordinary sentences and watch it get built. What did not fall is the part underneath: a machine does what you said, not what you meant. That was true of a 1946 punch card with one hole out of place, and it is true of the most advanced model running today.
So the expensive skill was never typing. It was deciding — precisely, out loud, in advance — what should happen, and making that meaning survive the trip out of your head. Every era of software made the telling easier. None of them made the deciding easier, and now that the telling is nearly free, the deciding is the whole job.
It has a name — prompt engineering — and most of what's written about it is folklore about magic words. It isn't that. It's clear thinking, written down, checked against reality. Which means it can be taught, practised, and proven.
Spreadsheets were once specialist software with a training industry around them. Then they became a thing everyone in an office was simply expected to be able to use. Describing software well is on the same path — early enough that doing it properly still stands out.
The skill isn't tied to one tool or one company's buttons. Hearing what a client actually needs, sizing a first version, saying what "done" means, insisting on evidence — that transfers to whatever you use next, and to work that has nothing to do with software.
This is the unusual part. Most soft skills you can only claim. Here, a machine drives your app and reports what it observed — so "I can build a working booking system" stops being a claim and becomes a link someone else can open.
What we won't promise you
We won't tell you this replaces a computer science degree, or that five days makes you a software engineer, or quote you a salary. Nobody can honestly promise where a skill takes you.
What we can promise is narrow and real: you will finish having built working software, you will understand every step you took, and you will hold receipts that anyone can verify without trusting you. What you do with that is yours.
