The word cloud is doing damage, and it has been doing it since before this class started. Every student in this room has been told for years that files go to the cloud, that photos are backed up to the cloud, that an app runs in the cloud. The word has been used so many times that it has stopped meaning anything, and a word that means nothing is worse than no word at all, because it stops the question before the question gets asked.
Here is the question it stops. Where is it?
Not a philosophical where. A street address. Every file anyone has ever described as being in the cloud is written on a physical drive, in a physical machine, in a rack, in a room, in a building, in a city. The drive is real. It has a size. It wears out after a few years and gets replaced. Somebody screwed it into the rack. The building it sits in has a roof and a parking lot and an electricity bill that runs into the millions of dollars a year, and it is cooled constantly, because thousands of machines doing arithmetic produce enough heat to make a room unusable in minutes.
None of that is hidden on purpose. It is just not interesting to say, so nobody says it, and the word cloud fills the gap with a picture of vapor.
Now take the next step, which is where the day earns its keep. If the building is in a place, then it is in a country, and countries have laws. The rules about what a company may do with what sits on its drives are not the same everywhere. What may be read, what may be kept, how long it may be kept, and who may demand a copy of it are decided by where the machine is, not by where you are.
That last part surprises people. A student in New Orleans using an American app may have their writing stored on a drive in Ireland, or in Singapore, or in Virginia. A company chooses where to put a building for reasons that have nothing to do with any individual using it: cheap electricity, cool weather, tax terms, distance to a large population. The choice gets made once, in a meeting, and after that everything typed into that app lands wherever that meeting decided it would land.
You are generally not told which building. It is not usually a secret in the sense of being hidden. It is written down somewhere in a document almost nobody reads. But the practical experience of using the service is that your writing goes into a box labeled cloud and an answer comes back, and nothing on the screen mentions a country.
This has a plain consequence, and it is worth stating carefully rather than dramatically. When you use somebody else’s machine, what protects your writing is whatever applies to that machine. Not what you assumed. Not what you would have picked. What comes with the building.
Which is exactly why the rig matters next week.
The machines that will answer this class’s prompts are a few miles from this room. They are not in Ireland and they are not in Virginia. They are in a house in New Orleans, and the person who owns it is standing at the front of the room. When this class says that nothing is kept, that is not a promise inside a document written by a company nobody can inspect, about a building whose location nobody knows, under rules nobody read. It is a claim about two specific machines, in one specific place, that a student could in principle walk over and look at.
That difference is the entire reason for running a model in a house instead of renting one in a building, and it is a difference that only makes sense once the cloud has stopped being a shape in the sky and become what it actually is. Somebody’s computers. In somebody’s building. Somewhere. And somewhere is a real place with its own rules.
Every question on this half of the classwork asks about that in a different way. If a student can answer them by thinking about a building instead of a cloud, the day landed.
The words, in plain terms
Arc: the network. A loop, not a line. Five numbered stages out to an AI data center, and a return path in a different colour bringing the answer all the way back into the building it started in. Say that the whole trip happens every time anyone presses send, because students picture one connection that stays open.
Stage 2 is drawn as one box and labelled as a simplification, because the traceroute finds three pieces of equipment inside this building before anything leaves it. Point at hops 1 through 3 on the trace, the ones beginning with 10, and say that those three are inside this building.
Only one line is dashed, and the dash means the signal is in the air. Everything after stage 2 is solid, because after the router it is wire or glass the rest of the way. If a student can say why there is exactly one dashed line, they have the day’s first claim.
The last caption line points at Monday. Same loop, same five stages, and the far end is a house instead of a data center. Do not explain how that works today.
The words, in plain terms
Arc: the cloud is a building. This is the drill picture, and it works the same way 02b did. The left panel is the mental image the word cloud produces on its own: files floating, no address, no owner, no power bill. The right panel is a building with racks in it. Every slot in every rack is schematic 01 from Day 3. Not a new kind of machine. The same kind, thousands of times.
The words, in plain terms
Arc: the cloud is a building. A data center and a house, hanging off the same network, drawn at the same scale of detail on purpose. One holds thousands of machines and one holds two, each with its own card. The two cards are named, and they are the same 4090 and 5070 Ti that sat on the ladder in schematic 03e last week. Two bars that were arithmetic then are hardware now. Both are servers, because a server is defined by its job and not by its size. This is why a class can have its own.
The racks are drawn blank on purpose. Schematic 09 already said what is in them. The two cards in the house are named, and the two racks are not, and the line under each side says why: one of these is ours and one of them is somebody’s building in a city nobody in this room could name. That is the whole We Do reading, drawn.
Hold up the teacher Chromebook. It is on the same network as both boxes on this picture. It has 16 gigabytes of memory, which is more than most machines in this room. Can it go on this picture as a third box?
Reveal
No. And no amount of money spent on it would change that. Storage is fine, memory is fine, and the runtime box on schematic 07 is still empty, because what goes in that box is a program that talks directly to the machine, and ChromeOS does not run programs that talk directly to the machine. Every other limit in this unit was a number. This one is not.
That is what makes the claim on this picture precise. The data center and the house differ in count. The Chromebook differs in kind.
The words, in plain terms
Arc: the cloud is a building. Schematic 07 drawn again, as three steps read from the bottom up. Step 1, the file downloads to storage with room to spare. Step 2, it copies into memory, which is what load means, and the copy works. The file bar is drawn in both boxes on purpose. Copying did not move it, and after step 2 the file exists in two places at once. That is the correction 02b was built for and it gets a second pass here. Step 3 does not exist.
Walk it in that order out loud. Students expect the failure at step 1 or step 2, because every limit they have met in this unit so far has been a size. Both of those steps work. The arrow into step 3 is drawn dashed and going nowhere.
On the Day 3 version a student could still tell themselves the Chromebook failed because it was a cheap machine. This one takes that away.
Hold the actual machine up when this is on the screen. It is the only object in the room that beats most student Chromebooks on parts and still cannot do the job.
The words, in plain terms
Arc: the cloud is a building. A vendor illustration, used unedited, logo included. Schematic 09 claims the cloud is a building full of racks. This is that claim drawn by a company that sells the buildings.
The two workers are the thing to point at. Thousands of machines, two people on the floor. That is a true fact about how these buildings run and no description lands it the way the picture does.
It carries five labels this class is not teaching. Use two. GPU Accelerated Nodes is the cards. Liquid Cooling Loop is the heat the We Do reading describes. Leave the other three alone. A real diagram carries more words than a lesson does, and students should see that.
Say once that this is a drawing and not a photograph, and that a company made it in order to sell buildings like it.
The words, in plain terms
Arc: the cloud is a building. A single machine with the side panel off. This is the counterpart to the data center diagram and it is meant to be read against it. One cooling loop, one card, instead of thousands of each in a building.
Two things are readable without help: GEFORCE RTX printed on the card, and the block on the processor with tubes running off it to a radiator. The data center drawing labels GPU Accelerated Nodes and a Liquid Cooling Loop. Both are here, once each.
Show it beside schematic 12 and let students match parts across the two. The photograph proves the machine is real. The drawing says what everything is called and where the hidden things are.
Three of the five labels on the data center drawing are visible in this one case. The tubes running off the processor are a cooling loop. The card with GEFORCE RTX printed on it is a GPU node. The cable bundle is the power. One of each, instead of thousands of each, in a room instead of a building.
The processor is not in this picture. What sits where it should be is the cooler mounted on top of it, which is the single most important thing to say out loud while this is on the screen. Students will call that block the CPU otherwise, and they will carry that error into next week.
Say plainly that this is a machine like the two in the house, not a photograph of them. Schematic 10 claims we can name every part because it is ours, and that claim does not survive presenting a stock photo as the spare room.
The words, in plain terms
Arc: the cloud is a building. The chip itself, out of the machine, nothing on top of it. This is what was underneath the cooler in the previous picture.
Show it immediately after saying that the cooler is not the CPU. One picture raises the question and the next one answers it. Nothing else needs to be said about this image.
The words, in plain terms
Arc: the cloud is a building. The machine from the photograph, drawn, with every part named in the position it occupies. Processor, cooler, radiator, memory, graphics card, storage, power supply, fans.
Three boxes are dashed, and they are the three parts the photograph cannot show: the processor under its cooler, the memory in shadow behind cables, and the drive lying flat on the board under a metal cover. Those dashes are the whole reason this drawing exists beside the photo, and they are worth pointing at one at a time.
A photograph shows what is there. A schematic shows what it is called.
The words, in plain terms
Arc: the network. Unedited output from a real command run on a machine in this building, to this class’s own website. It exists to do one job: prove schematic 08 is not made up.
How to read it. Every numbered line is one hop: one piece of equipment the request passed through, in the order it passed through them. The three times on each line are three separate attempts, so the room can see the trip was consistent and not a fluke. The name or number on the right is the machine that answered.
Reading the ten lines.
1. 10.131.224.1 — First stop after your workstation. A switch inside this building. The 10. says the address is private and only means anything inside the school.
2. 10.132.251.1 — Another piece of school equipment, further along the internal network. Still a 10. address.
3. 10.132.251.254 — The last machine inside the school that answers this command. After this the request leaves the building.
4. Request timed out — A machine that took the request and was told not to reply to this kind of question. It passed the request along regardless. If the trip had stopped here, there would be no hops 5 through 10.
5. metacmtc01.no.no.cox.net — First machine outside the school. Owned by Cox. The no.no in the name is New Orleans.
6. dalsbprj02-ae2.rd.dl.cox.net — Still Cox, now in Dallas. The dl in the name is Dallas. About five hundred miles from hop 5, which is why the time roughly doubles.
7. 98.181.111.94 — The last machine on Cox’s side before the request enters somebody else’s network.
8. 141.101.74.78 — First machine owned by Cloudflare, the company that answers on behalf of muggsofcompsci.net.
9. 141.101.74.145 — Another Cloudflare machine, one step closer to the destination.
10. 104.21.7.78 — The machine that answers when you type muggsofcompsci.net. The reply travels back through this whole list in reverse.
The eleven on the drawing. Between hop 5 (New Orleans) and hop 6 (Dallas) the time roughly doubles: eight milliseconds becomes nineteen. The eleven on schematic 08 is that subtraction, measured rather than claimed.
The words, in plain terms
Arc: the network. The traceroute above, drawn on a map. Ten machines answered, and none of them is the machine that wrote the answer.
Read it the way the trace reads. Three boxes inside this building, all with 10. addresses. One dashed box for hop 4, which never replied — the request went on anyway. Two Cox boxes about five hundred miles apart, which is why hop 5’s eight milliseconds becomes hop 6’s nineteen. Three Cloudflare rows at the end. The dashed box past hop 10 is what the command cannot see, and neither can you.
The times do not add up. Every one is already a full round trip from your machine. The whole thing is the last one, about twenty milliseconds. When a model actually answers you the wait is longer than that, and the extra is the machine doing arithmetic — which happens somewhere past the dashed box.
- APeriod 1
- BPeriod 2
- CPeriod 4
- AHow fast is it?
- BWhere is it?
- CWho built it?
- DHow much does it cost?
- ASpread across many machines with no single location
- BWritten on a physical drive, in a machine, in a rack, in a building, in a city
- CHeld in the wires between cities
- DStored on the router in your building
- ABecause cold drives hold more data
- BBecause thousands of machines doing arithmetic produce enough heat to make a room unusable in minutes
- CBecause the building is usually in a hot country
- DBecause cooling is required by law
- AWhere the person who wrote it lives
- BWhere the machine holding it is
- CWhich app was used to write it
- DHow long ago it was written
- AThe preferences of the people who will use it
- BCheap electricity, cool weather, tax terms, and distance to a large population
- CThe country where the company was founded
- DWhere the fastest wifi is available
- AYes, the app displays the country before you type
- BNo, and it is deliberately hidden from everyone
- CGenerally not; it is written down somewhere almost nobody reads
- DYes, but only if you ask the provider
- AWhatever you assumed would protect it
- BThe rules you would have chosen
- CWhatever applies to that machine
- DThe rules of the country you are sitting in
- ABecause a machine in a house is always faster
- BBecause the claim about what is kept is about one specific machine in a specific place, not a document about a building nobody can locate
- CBecause houses are not connected to the internet
- DBecause local machines are not subject to any rules
- AThe cloud is unsafe and should not be used
- BThe cloud is somebody’s computers in somebody’s building somewhere, and somewhere is a real place with its own rules
- CFiles should always be stored on your own device
- DData centers are too expensive to build
- ANone
- BOne
- CThree
- DAll four
- AYour device and the building’s equipment
- BThe building’s equipment and your provider
- CYour provider and the long lines
- DThe long lines and the data center
- AAt the provider
- BAt the long lines
- CAt the router, inside the building
- DAt the data center
- A3 ms
- B11 ms
- C20 ms
- D30 ms
- AIt is drawn with a dashed outline and says the cloud has no address, no owner, and no power bill
- BIt has more machines in it than the right panel
- CIt is drawn larger than the right panel
- DIt has no label
- AA different kind of computer built only for data centers
- BSchematic 01: RAM, CPU, storage, and on many of them a card
- CA copy of the model file
- DCooling equipment
- ARTX 4090 with 24 GB, and RTX 5070 Ti with 16 GB
- BRTX 4060 with 8 GB, and RTX 4090 with 24 GB
- CRTX 5070 Ti with 24 GB, and RTX 4090 with 16 GB
- DTwo RTX 4090s, each with 24 GB
- AThe provider
- BThe network
- CThe cloud
- DThe router
- AThe number of machines it holds
- BThe size of the building it is in
- CThe job it does, which is answering requests from other machines
- DWhether it is owned by a company
- ANone
- BTwo
- CSix
- DMore than twenty
- ALiquid Cooling Loop
- BRedundant Power
- CGPU Accelerated Nodes
- DHigh-Speed Networking
- AHigh Density Compute
- BLiquid Cooling Loop
- CRedundant Power
- DHigh-Speed Networking
- AThat the racks contain machines
- BThat the building has an address
- CCooling, power, and the people who work on the floor
- DThat the machines are connected to a network
- AOne
- BTwo
- CThree
- DNone
- AThe fans and the power supply
- BThe cooler and the radiator
- CThe memory and the storage
- DThe graphics card and the processor
- AThe graphics card
- BThe cooler, keeping it from overheating
- CThe power supply
- DThe memory
- AThe drawing shows parts the machine does not really have
- BThe photograph shows what is there; the drawing shows what each part is called and where the hidden one is
- CThe drawing is a picture of a newer machine
- DThe photograph is not a real machine
- AThe single machine has parts the data center does not have
- BThe data center has parts the single machine does not have
- CBoth have cooling, power, and cards, in different numbers
- DNeither picture shows a card
- AHops 1, 2, and 3, the ones starting with 10.
- BHops 5, 6, and 7, the ones with cox.net in the name
- CHops 8, 9, and 10
- DHop 4, the one that timed out
- AOne of the machines is broken
- BThe request crossed a long line between cities, and distance costs time
- CThe provider stored the request for a moment
- DThe request went back into the air
- ANeither one can hold the 6.63 gigabyte file
- BBoth have more VRAM than 6.63 gigabytes, so both can hold the file
- COnly the 4090 can hold the file
- DThe ladder did not include either card
- AIt never downloads
- BIt downloads to storage but will not copy into memory
- CIt downloads to storage and copies into memory, then stops
- DIt runs, but slowly
- AOne, in storage
- BOne, in memory
- CTwo, in storage and in memory
- DNone, it disappears
- AIt does not have enough memory
- BIt does not have enough storage
- CIts runtime box is empty, and no amount of memory or storage fills it
- DIt is not connected to the network
- AThe data center machines have no cards in them
- BNobody in this room knows which cards are in that building, or which city it is in
- CThe racks are too small to label
- DThe data center uses a different kind of card
The first item is your name. Answer it — that is what puts you on the work now that email collection is off.