Part two ended on compression as the throughline — fifteen years of handing engineers three sentences instead of a design doc, turning out to be the exact same discipline as handing a model three sentences instead of one. This one is about the limit case of that discipline: the two-word instruction that compresses everything down to nothing and just says "figure it out."
Here's what it was actually attached to. A networked 10v10 match connects clean — camera works, a cube renders, the client joins a real match for the first time. And then, instantly, "YOU WIN." No fight, no movement, no real opponent. "I won upon connection" — the win registers on the handshake, not after any play. "Something about the win conditions isn't set up right." Then the line that actually mattered: "you said to not design the system too much before 1v1 works but too late" — wry, self-aware, not a complaint. The 10v10 pivot had outrun verifying the one thing that was supposed to be verified first. And then: "figure it out."
Two words. No file name, no stack trace, no hypothesis about where to look. Compare that to part two's three-sentence ticket, still generous by comparison — a ticket names a symptom, points at a subsystem, gives the recipient somewhere to start. "Figure it out" gives nothing but a boundary: somewhere in this codebase is a wrong answer, go find it. That's not a lazier instruction than a detailed one. It's a *harder* one, because all the compression that a written ticket would normally do for you — narrowing the search space, ruling out wrong turns in advance — now has to happen on the other end, live, with no help.
Which is the actual point, and it's worth being precise about what "figure it out" is really asking for, because it's not "solve this problem." It's "hold the problem yourself." The instant "YOU WIN" had a real, wrong first hypothesis — a team-initialization bug, hero state not fully set before the first tick evaluates the win condition — and the honest move was to say so and not fix it, flag instead of guess. That's not what "figure it out" was asking for either. It doesn't mean stop at the first plausible story. It means keep going until the story is load-bearing: `grep` for the actual pattern, read the actual call sites, find that three separate `#ifndef _WIN32` guards — reintroduced by newer code, after an earlier fix had already closed the same class of bug once — were silently routing a Windows client into a local single-player simulation instead of ever touching the real match. Silent, not a compile error. The kind of thing that looks like it's working right up until someone actually plays it.
That's the part standup-you and 3am-you would both recognize from part two, pointed at a different target. In a standup, "figure it out" would be praise — a lead trusting a senior engineer with an ambiguous problem instead of micromanaging the fix, the highest compliment compression can pay. At 3am mid-direction, deployed instead of performed, it's not praise or an insult — it's a resource-allocation decision. The founder already knows the fix requires reading real code, not receiving a hypothesis; saying more wouldn't have gotten there faster, it would have just front-loaded a guess that might have been wrong. Two words, correctly sized to the actual information the sender had, which was: something is broken, I don't know what, go find out.
The honest ending here isn't "and it worked" — obviously it did, or this wouldn't be worth writing up. The honest ending is that the two words did exactly the amount of work they were supposed to do and no more: they didn't solve the bug, they refused to solve it on the sender's behalf, which is the only way the actual fix — the one that required someone to sit with the real file and find the real pattern — was ever going to get found instead of guessed at. "Figure it out" isn't the absence of a prompt. It's the prompt with everything stripped off except the one thing that matters: the confidence that the recipient can carry the rest.
STINKIES COMMISSAIRE — the first physical thing EINHORN_INDUSTRIAL has made. Join the waiting list for the hoodie →
← All posts