Devs structures itself around the cruelest possible editing choice: it never lets you see the machine work.
When Lyndon reaches a computational breakthrough, the camera cuts — and when the team approaches the final proof, the season ends, which isn't suspense so much as something meaner: the show arguing that determinism, once completed as a system you can actually perceive, becomes psychologically uninhabitable.
Watch the moment Katie and Lyndon stand before the completed visualization in episode seven. They can see the past and the future — the image is right there on the screen, flowing, inevitable, total — but then Amaya interrupts, Codify interferes, and the moment shatters because the show doesn't let us sit in the aesthetic of total knowledge long enough to feel what living inside it would actually demand.
The pacing architecture confirms this. Devs moves glacially through philosophical argument, then sprints through action, then stalls again — rhythms that prevent you from ever settling into belief. You never get the long, quiet scene where a character accepts determinism fully and lives the next day unchanged, because that scene would expose the central horror: that knowing the future and accepting it are neurologically incompatible.
We need uncertainty not as a flaw in our knowledge systems but as the baseline condition that lets consciousness function at all — and the show's refusal to end isn't narrative failure, but a confession about what determinism actually asks of us, which is more than we can pay.
Watch the sequence where Katie and Lyndon observe the complete timeline visualization (season 1, episode 7, approximately 38-42 minutes), then pause when the image shatters—and sit with what the show refuses to let you see sustained.
Read Alex Garland's interview with Vulture (March 2020) where he discusses why he chose not to depict the machine's actual mechanics visually, and what that choice meant for the audience's relationship to the concept itself.