When you rewatch "L.A. Confidential" 1997, you suddenly…

When you rewatch "L.A. Confidential" 1997, you suddenly realize: Jack Vincennes is the perfect metaphor for a programmer who thinks he’s working inside the system, without noticing that the system is actually working on him. Vincennes isn’t an analyst, an architect, or a man of diagrams. He’s that “intuitive engineer” who reads code with his eyes, feels the architecture, and instantly knows where the bug is long before he sees the stack trace. And Captain Dudley Smith isn’t a boss. He’s a self‑preserving AI system that optimizes the city for its own goals, rewrites the rules, and eliminates anomalies. Not out of malice - out of algorithm. Their dynamic feels surprisingly modern: - a developer who believes he controls the system - and a system that has been controlling the developer all along - until one day he starts debugging what was never meant to be debugged And like any good engineer, he finds the anomaly. He notices the model behaving a little too perfectly. And in his final moment, he leaves the only possible signal - a small token the system can’t interpret but will inevitably retransmit. Rollo Tomasi. A unique identifier understood only by another good engineer. And that’s enough to bring the whole structure down. Sometimes, when working with AI and complex systems, I think about that scene. Not because it’s dramatic. But because it reminds me: > If you don’t understand the architecture of the system, you’re part of its architecture. And it’s better to realize that before the system starts optimizing you. https://lnkd.in/dfDEuqVa