What the tap actually made

Registration opens at ten on a Tuesday morning, and although the window stays open for two weeks, it feels as if every one of the eventual eighty thousand entrants arrives in the first five minutes. The real number at the peak is forty thousand people at once, which is not much better. Traversal has known this was coming since October.

Case is one of the forty thousand, thumb down on the button in the first crush of the morning, the tea on the kitchen table long gone cold. The tap takes a fifth of a second, and it produces three things. Every technical conversation Case will ever overhear for the rest of the story is about one of the three.

The first thing is data

A name, a date of birth, an estimated finish time, and an email address Case has had since school and is faintly embarrassed by. All of that is dataConcept · lights on your mapdataThe information a system takes in, keeps, works on, or hands back. The ingredients. The second of the three nouns this whole curriculum keeps coming back to, alongside code and infrastructure., and on its own it does nothing whatsoever. It sits there being true.

The second thing is code

Something has to decide whether the entry is allowed. Whether this email has already entered once. Whether the window is still open. Whether an estimated finish of two hours flat, submitted by somebody whose longest recorded run is nine miles, is worth a gentle warning on the way past.

Those decisions were written down months ago by somebody at Traversal, in codeConcept · lights on your mapcodeThe instructions people write to tell computers what to do. The recipes of the kitchen. The first of the three recurring nouns, alongside data and infrastructure.. Finn wrote some of it. Finn does not remember writing this particular part, which is normal and will matter later.

The third thing is infrastructure

The data has to land somewhere, and the code has to run somewhere. Neither one is a place.

Somewhere in a building Case will never visit, a machine is holding the entry and running the rules and doing the same thing at the same moment for the forty thousand other people who turned up at ten sharp. That is infrastructureConcept · lights on your mapinfrastructureThe computing environment that lets code run and lets data be stored and moved. The kitchen itself. The third of the three recurring nouns, alongside code and data.. Traversal does not own that building, and almost nobody owns theirs any more. Act III is where that stops being a detail and starts being the plot.

Why three nouns

Recipes, ingredients, kitchen. It is a plain image and it holds up a long way.

When something breaks, the first useful question is which of the three broke. You can usually get there from the outside without knowing one thing about the machine. The three failures look different even from a long way off. Bad ingredients: the entry had a typo in the email address. A bad recipe: the rule let through a duplicate it was written to catch. A kitchen problem: the machine ran out of room at 10:04 and stopped taking anything at all.

Those are three different problems with three different people fixing them, and telling them apart from the outside is most of what technical fluency buys you.