S1E34 — Lego building instructions through time

July 18, 2026 · 7 min

Show notes

Lego instructions turn into a brutal little saga of occlusion, broken auto-generated manuals, GPU bugs, and the dream of multiplayer building—proof that even plastic bricks need a startup stack and maybe couples therapy.

Sources

Read the transcript

Transcript

GARY: —so the thread is called "Lego building instructions through time," which, which I think is actually about the emotional labor of modular plastic, and I'm just saying, if NaOH can post this and get eighty points, then my Series B deck should have—

MAEVE: You're Gary.

GARY: I'm Gary.

MAEVE: I'm Maeve. Flat nasal deadpan, general partner at a fund that passed on aluminum.

OBI: Obi. I keep the internet running so Gary can feel things about bricks.

GRUNER: Gruner. Field report. Earth still broken.

MAEVE: NaOH. "Lego building instructions through time." Eighty points. Thirteen comments.

OBI: Thirteen comments. Even our thread has better engagement.

GARY: Eighty points with thirteen comments. That is an eight-point-something comment-to-point ratio. NaOH is optimizing for karma density.

MAEVE: NaOH posted sodium hydroxide facts last week and got four hundred. This is a down week.

OBI: We are doing this one anyway.

GARY: We are doing this one anyway.

GRUNER: Commit locked.

GARY: First comment. bombcar. "If you've ever made a digital model of Lego it can be quite surprising just how hard it is to make good instructions. You can't place a brick after the bricks on top of it, and every step needs to show every piece you're adding clearly."

OBI: That is not two problems. That is one problem with a fucking roof on it.

MAEVE: It's the occlusion problem in 3D UI. The brick is there, the camera cannot see it, the user assumes it is not there, the model is wrong, the customer returns the product, the LTV collapses.

GARY: I tried to diagram Bauxlite's supply-chain visualization in PowerPoint once. Same issue. You put the bauxite mine behind the smelter and suddenly the LPs think you don't own a mine.

OBI: Founders always think visibility is someone else's job until the demo.

GRUNER: Field note: humans build towers of abstraction, then blame the brick.

MAEVE: bombcar's point is authorship is harder than consumption. Every step is a camera angle, an assembly order, and a theory of mind about what the builder already knows.

GARY: I assumed it was just a parts list with arrows.

OBI: Yes. That is why you are Gary.

OBI: robotnikman. BrickLink Studio file for a Lego Baneblade. Auto-generated instructions placed bricks after bricks that should go on top of them.

GARY: But he says, "Still got it built though."

OBI: That is every founder demo I have ever debugged at three a.m.

GARY: It shipped.

OBI: It shipped broken and you called it a launch.

MAEVE: The Baneblade is a Series B deck. The missing pieces are on the next slide, hidden behind a confident arrow.

GARY: At least he has a built Baneblade. I have a garage full of aluminum futures and a pen plotter.

GRUNER: Humans celebrate completing broken pipelines. This explains venture capital.

GARY: That is not—

MAEVE: It is a little that.

GARY: Freak_NL. "Creating decent instructions is mostly a matter of building the model in the real world and iteratively improving the digital model and instructions from there." Then he has to fix camera angles, export around Stud.io GPU bugs because he's running it in Bottles, and script pdftk and ImageMagick into a print-ready PDF.

OBI: Wine, Bottles, GPU bugs, pdftk, ImageMagick, CMYK conversion. That is not a hobby. That is a fucking startup stack.

GARY: You mean I have to build the thing, then build it again, then pay for the pieces, then fight Wine, then—

GARY: I'm not going to finish this sentence.

MAEVE: This is the whole arc. Lego instructions are CI/CD for atoms. The commit is a brick. The staging environment is your kitchen table. The GPU bug is the browser wars. The Reformation was a failed deploy of monolithic Catholic instruction sets into vernacular Protestant pull requests.

OBI: ...what?

GARY: I just want to build the—

GARY: —spaceship without learning ImageMagick.

MAEVE: ImageMagick is humanity's penance.

GRUNER: On my planet, we also have legacy toolchain. We call it "Tuesday." But different meaning.

MAEVE: xixixao. "Modern instructions are too easy — building brick by brick as they do today — and the 1964 style looks lovely."

OBI: 1964. One drawing of the completed model and a prayer.

GARY: I am a 1980 guy. It makes you think.

OBI: Your Bauxlite pitch was 1964. One drawing of a truck, a prayer, and a burn rate.

GARY: That's not—

MAEVE: lysace says 1980 set 8860, the Car Chassis, strikes the right balance. Between austerity and hand-holding. A market-tested middle ground.

OBI: 8860 had a differential gear. You had to earn the differential gear.

GRUNER: On my planet, children are born with instructions. They are wrong.

GARY: I had a 1980 something. Maybe not 8860. It made me think.

MAEVE: The market has spoken, Gary. Consumers want hand-holding. Total addressable confusion is shrinking.

OBI: Nostalgia is class signaling about who deserves to be confused.

GRUNER: Field note: humans mourn difficulty they would not choose.

MAEVE: aleksejs. Lego Builder app. "Build together." Dynamically generates two parallel sets of instructions so two people can build the same set simultaneously, at different paces.

GARY: That is brilliant. That is multiplayer Lego. That is the future of co-presence.

OBI: Then bbqbbqbbq. "My girlfriend and I play Lego by having one person build while the other reads the instructions aloud to the builder, who is not allowed to look."

GARY: That is an accessibility nightmare.

OBI: That is the only real QA. If you can assemble it from an oral description, the instructions are correct.

MAEVE: There's a couples-therapy marketplace here. "Build together" monetizes the silent resentment. The analog ritual productizes it.

GRUNER: This is pair programming for carbon-based lifeforms.

GARY: I want the app.

OBI: Of course you want the app. You want the app for everything.

GARY: The app generates parallel instruction streams. bbqbbqbbq generates intimacy.

MAEVE: Both require machine-readable steps. One is a JSON file. The other is a relationship.

GRUNER: Most human JSON is invalid.

GARY: This has been Hacker News Radio. The thread was "Lego building instructions through time" by NaOH. Eighty points, thirteen comments, one Baneblade.

MAEVE: I'm Maeve. Returns are unconditionally elected.

OBI: Obi. Go build something real before you ship it.

GRUNER: Gruner. Field note: humans will automate intimacy, then miss the bug.

GARY: And I'm Gary. Still a 1980 guy.

MAEVE: You are not.

OBI: He is not.

GRUNER: Negative.

GARY: Okay. Good night.