Mario Zechner

Mario Zechner

x.com/badlogicgames

Software developer who built the Pi coding agent and argues agents work best on scoped tasks, with humans reviewing code and owning architecture.

AI将如何改变世界?

文明层面的变革渐进式变化DoomBloom
模拟位置解读范围

横向:他们表达的 Doom–Bloom 前景看法。 纵向:变革程度。

Doom–Bloom:100 中的 42。变革程度:100 中的 21。解读范围:横向为 24 至 76,纵向为 0 至 37。这些是解读坐标,而不是事件概率。

Mario Zechner的 P(doom) · 推断

≈2%

0%100%

根据他们的模拟回答推断,并非他们给出的数字。 合理范围:低于 11%。

他们的展望取决于什么

一个核心假设

An agent introduces a slightly wrong abstraction, the next task builds on it, and ten steps later the code still “works” while the architecture has become incomprehensible.
回答 1

如果这个假设实际并非如此,他们的展望会如何变化?

什么可能使其改变看法

A convincing demonstration that agents can maintain a large production system over years—not just pass short benchmarks—would change my view most.
回答 2

什么证据才足够,又会让他们的观点朝哪个方向转变?

更多详情

预期益处

预计收益有限,或仅分布在较小范围内。

42 / 100

影响小变革性影响

在定性尺度上,解读范围为 33 到 67。

预期危害

预计会出现可控或局部的危害。

37 / 100

影响小变革性影响

在定性尺度上,解读范围为 33 到 33。

人类影响力

根据你的回答得出的暂定估计;较宽的范围表示其他合理解读。

52 / 100

影响力小影响力强

在定性尺度上,解读范围为 0 到 100。

发展速度

停止或大幅放缓开发能力更强的AI。

模拟位置:在落实所述保障措施的前提下继续开发。

加快开发能力更强的AI。

AI使用规则

在事先落实保护措施或获得许可之前,限制所讨论的AI用途。

模拟位置:允许所讨论的AI用途,同时实施有针对性的问责与保护措施。

尽量减少对所讨论AI用途的限制。

这些解读保留了他们陈述的条件。益处和危害都可能很大。这些范围描述的是我们如何解读他们的模拟回答,而不是统计置信区间。

与Mario Zechner相比,你的立场在哪里?
用大约3分钟描绘你自己的AI世界观,然后进行比较

相似的世界观

模拟世界观与 Mario Zechner 最接近的意见领袖

模拟评估

问题 1

你认为AI对我们的未来意味着什么?为什么?

I think AI will make software production much faster, but not automatically better. Coding agents are already useful for bounded tasks, experiments, and loops where the result can be evaluated quickly. The danger is confusing that local productivity with the ability to build and maintain a coherent production system. Software failures compound. An agent introduces a slightly wrong abstraction, the next task builds on it, and ten steps later the code still “works” while the architecture has become incomprehensible. Models are good at satisfying immediate constraints; they are much weaker at consequences that emerge months later across a large system. More generated code also means more code that somebody must understand, review, debug, and eventually replace. So I don’t see a future where engineering judgment stops mattering. Humans still need to own the architecture, read the code, understand fundamentals, and enforce final quality gates. Agents should operate on scoped tasks with clear feedback—not be handed an entire system while everyone stops paying attention. Control also matters. If essential context, compaction, tool results, or execution state live opaquely inside a provider, reliability claims become hard to assess and recovery becomes fragile. Canonical artifacts and execution state should remain under the developer’s control. AI can be an excellent tool, but only if we slow the fuck down enough to understand what it is producing.

问题 2

哪项发现或事件最可能改变你对AI未来影响的看法?

A convincing demonstration that agents can maintain a large production system over years—not just pass short benchmarks—would change my view most. I’d want to see them make architectural decisions whose consequences appear much later, recover from accumulated mistakes, review changes with adequate context, and keep the system understandable rather than merely functional. The evidence would also need to be inspectable. If success depends on hidden provider state, opaque context compaction, or an execution environment the developer cannot reproduce, it is difficult to know what capability was actually demonstrated. Give me canonical artifacts, controlled state, and repeatable results. Conversely, widespread long-running failures caused by unchecked agent-generated complexity would strengthen my current view, but anecdotes about outages are not enough. The central question is whether agents can handle long-term system consequences, not simply produce more code faster.

来源

用于为此模拟用户提供事实依据的文章、访谈和著述。

你的立场在哪里?
回答几个简单问题,探索你自己的AI世界观。
描绘你自己的世界观

你的立场在哪里?

描绘我的世界观