Describe It, Build It, Own It

Describe the software you want in plain words, build it, and be able to explain every part of it.

This page lists what a learner is able to do at the end of this class. It does not carry the class itself. The lessons, exercises and answers stay in the classroom and in the book.

What you will be able to do

What the class is really about

The last class is the one all the others were for. You build a working piece of software, on your own, by describing it.

No code is typed. You write down what you want, in plain words, as carefully as you can manage. AI produces it. You run it, find out what is wrong, say what needs to change, and go round again. Describe, generate, run, test, improve. Most learners go round that loop four or five times before they are satisfied, and the going round is where the learning actually sits.

What people build is small and real. A calculator. A quiz. A simple game. A tool that does one job they genuinely wanted done. It opens in a browser and it works, and they made it on a Saturday having never programmed before in their lives.

The condition attached to it is the important part. At the end you have to explain your own project, in ordinary language, to somebody else. Not the code line by line, but what it does, how the parts fit together, and why you made the choices you made. If you cannot do that, you did not build it. You only requested it.

That distinction is the whole course in one sentence. AI can extend what you are able to make by an enormous amount, and it can do it for somebody who has never written a line of code. What it cannot do is your thinking. The moment you hand that over, you lose the ability to tell whether what came back is any good, and that is the one thing nobody can check for you.

Careful use

Creative direction. Understanding what you made, explaining it, and saying what AI did.

Careful use is not a separate lesson at the end of the course. A piece of it belongs to every one of the eight classes, and this is the piece that belongs to this one.

How this class is taught

  • One core concept. The class carries a single idea. Nothing is covered twice and nothing is rushed.
  • Hands before theory. You do the thing first. The explanation lands better once you have seen what happened.
  • Practice in company. Weekday slots in the lab follow the weekend class, with somebody there to help.
  • Mixed ages at one table. The youngest in a batch may be ten and the oldest past fifty. Each takes something from the other.

Chapter 7, Speak, See, Create

All eight chapters

How to apply