March 22, 2026
Roll dice, write bytes
Coding as a Game of Probability
Dev world split: Lucky dice roll or logic-driven code
TLDR: The piece argues AI coding is navigating chances: tight, specific requests work; vague, big asks wobble. Commenters split between “LLMs are fine with good specs” and “use logical solvers, not guessers,” exposing a real tension over whether AI is a handy assistant or a hype-fueled coin toss.
Forget dry think pieces—devs are treating this as a cage match. The author says coding with AI is like steering through a tree of possible outcomes: narrow requests (like “black page, white square”) are easy wins, while vague goals (“make Snake”) are a carnival target. The crowd? Loud and divided. One camp cheers: keep prompts tight, iterate fast, and AI shines when the output is smaller than the input (think summaries). Another camp fires back: real work is messy and abstract; “vibe coding” won’t ship your ERP.
The spiciest spark comes from derrak, who asks why we’re using statistical guessers at all—why not logic engines that solve puzzles step by step, like SAT and SMT solvers? That kicked off a thread of "math brains vs. autocomplete" memes. Pragmatists shrugged: LLMs are great when your spec is tight; the rest is user error. Skeptics clapped back: if AI can only nail the easy stuff, it’s a novelty, not a coworker.
Meanwhile, the humor flowed: “Choose-your-own-adventure commits,” “coin-flip intern,” and a new rule of thumb—wide goalposts make for viral demos, narrow paths make for real paychecks. Translation: AI can one-shot a toy, but for grown-up projects you either write a real spec or prepare for chaos.
Key Points
- •The article conceptualizes AI-assisted coding as navigating a probabilistic decision tree from input to output.
- •Highly specific prompts produce more reliable, narrow-path outputs; broad prompts lead to varied but acceptable outcomes.
- •Real-world software work requires iterative discovery to translate abstract goals into precise code, limiting one-shot effectiveness.
- •AI coding success is linked to the ratio of input detail to output scope; more input constraint typically improves outcomes.
- •An ERP project example, including adding an API route, is cited to illustrate how this input-output balance applies at task level.