Software RecetaMODULE 0 · LESSON 1

What software is

All lessons

Loading the lesson…

Transcript

Read the lesson: What software is

Every word the lesson says, in order.

Here's a promise. By the end of this short lesson, you'll be able to look at any app on your phone — your notes, your bank, your favorite game — and break it down into three plain parts.

No code yet. Just a new way of seeing.

So here is the big idea, as simply as I can say it. All software is three things: Shape, Memory, and Movement.

Every program ever written, from a tiny calculator to a giant social network, is some mix of those three.

Let's find all three inside a place you already understand: a restaurant kitchen, in the middle of a busy dinner.

First, the pantry. Flour sits in a wide, open bin, because you scoop from it. Spices sit in small pots with tight lids, because you only need a pinch. Every container fits what's inside it.

That's Shape. Its proper name is Matter. It's the form information takes, so you can find it and use it.

Second, the fridge and the recipe book. The fridge keeps prepped food cold until service. The recipe book keeps what the kitchen knows, long after the lights go off.

Some things stay for minutes, like a pot kept warm on the side. Some stay for years. That's Memory. Its proper name is Persistence. It's about what stays.

Third, the line. An order comes in on a ticket. The plate moves from the grill, to the garnish, to the pass, and out to the table.

That's Movement. Its proper name is Motion. It's information going from one place to another: coming in, going out, handed along.

The pantry is Shape. The fridge and the recipe book are Memory. The line is Movement. A whole kitchen in three parts — and a whole world of software, in the same three.

Two small words will follow you through every lesson: read and write. To read is to look at something without changing it, like a cook reading the ticket. To write is to set it or change it, like a cook writing a new one.

And here's the rule this course is built on: read before you write.

So when you meet a confusing app, you don't have to understand all of it at once. Ask it three calm questions.

What is its Shape: what information does it hold? What is its Memory: what does it keep, and for how long? What is its Movement: what comes in, and what goes out?

And notice the order. You can't remember something until it has a shape. You can't move something until it's been kept somewhere. Shape first, then Memory, then Movement — each one resting on the one before.

Try it on a messaging app. Its Shape is messages. Its Memory is your chat history. Its Movement is the message you send, and the reply that comes back.

You won't always be exactly right at first, and that's fine. The point is to start seeing in threes.

That's the foundation: three things, and two verbs. In the next lesson, we'll meet read and write up close, and you'll run your very first line of real code.