The show's central mistake is treating determinism as its own punishment.

It isn't—what breaks people in Devs is that Katie Rinn, a person with documented psychological instability and personal investment in specific outcomes, interprets the machine's outputs and tells them what to do.

The machine never appears on screen as a comprehensible thing. We see Katie's face watching it, we see her making decisions, but we never see the architecture, the query language, the error margins, the audit trail—and this design choice isn't hiding the mystery to preserve it, it's embedding the actual mechanism of real power: making people accept conclusions from a system they cannot examine.

Watch how the show structures revelation. Every time someone gets proximity to the machine—Lily, Forest, Jamie—they don't gain understanding; they gain a Katie-filtered interpretation of what the machine supposedly said, then watch their lives compress into that reading. The pacing of Devs mirrors regulatory capture: long stretches of uncertainty punctuated by Katie's pronouncements, and people can't appeal, there's no second opinion, the machine's outputs are treated as law, but the inputs, the code, the methodology remain sealed.

This is why the show's refusal to resolve resolves nothing—the quantum computer is a red herring, and the actual plot is watching intelligent people operate under a system of forced epistemological dependence that in the real world isn't a physics problem but a regulatory one, which is why your bank's algorithm denies you credit, your email goes to spam, your parole algorithm recalculates your release date, and the explanation you get is always from someone's interpretation of a system you're forbidden to audit.