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.

Bagaimana AI akan mengubah dunia?

Perubahan peradabanPerubahan bertahapDoomBloom
Titik tengah rentang yang belum ditentukanRentang interpretasi

Mendatar: pandangan Doom–Bloom yang mereka ungkapkan. Ke atas: skala transformasi.

Doom–Bloom: 49 dari 100. Skala transformasi: 50 dari 100. Rentang interpretasi: 44 hingga 76 secara horizontal, 0 hingga 100 secara vertikal. Ini adalah koordinat interpretasi, bukan probabilitas kejadian.

P(doom) Mario Zechner · disimpulkan

≈2%

0%100%

Disimpulkan dari jawaban simulasi mereka, bukan angka yang mereka berikan. Rentang yang masuk akal: di bawah 9%.

Cara kami mengestimasi P(doom)

Hal-hal yang menentukan pandangan mereka

Asumsi utama

If humans stop reading the output, weak assumptions become abstractions, those abstractions become dependencies, and the consequences may appear long after the agent’s short evaluation loop has ended.
Jawaban 3

Jika asumsi ini ternyata berbeda, bagaimana pandangan mereka akan berubah?

Hal yang dapat mengubah pandangan mereka

The biggest update would come from long-running evidence that agents can independently maintain real production systems without architectural decay.
Jawaban 5

Bukti apa yang akan memadai, dan ke arah mana bukti itu akan mengubah pandangan mereka?

Detail lebih lanjut

Manfaat yang diperkirakan

Manfaat besar diperkirakan akan terwujud, dengan syarat penting atau keterbatasan distribusi.

65 / 100

Dampak kecilDampak transformatif

Rentang interpretasi 67 hingga 67 pada skala kualitatif.

Kerugian yang diperkirakan

Kerugian yang dapat dikelola atau bersifat lokal diperkirakan akan terjadi.

40 / 100

Dampak kecilDampak transformatif

Rentang interpretasi 33 hingga 67 pada skala kualitatif.

Pengaruh manusia

Pilihan manusia dapat mengarahkan ulang lintasan AI secara signifikan.

65 / 100

Sedikit pengaruhPengaruh kuat

Rentang interpretasi 33 hingga 92 pada skala kualitatif.

Laju pengembangan

Hentikan atau perlambat secara signifikan pengembangan AI yang lebih mampu.

Posisi simulasi: Lanjutkan pengembangan dengan perlindungan yang telah ditetapkan.

Percepat pengembangan AI yang lebih mampu.

Aturan penggunaan AI

Batasi penggunaan AI yang dibahas hingga perlindungan atau izin sebelumnya tersedia.

Posisi simulasi: Izinkan penggunaan AI yang dibahas dengan akuntabilitas dan perlindungan yang terarah.

Minimalkan pembatasan terhadap penggunaan AI yang dibahas.

Interpretasi ini mempertahankan kondisi yang mereka nyatakan. Manfaat dan kerugian dapat sama-sama besar. Rentang tersebut menggambarkan cara kami membaca jawaban simulasi mereka, bukan interval kepercayaan statistik.

Di mana posisi Anda dibandingkan dengan Mario Zechner?
Petakan pandangan dunia AI Anda sendiri dalam waktu sekitar 3 menit, lalu bandingkan

Pandangan dunia serupa

Pemimpin opini dengan pandangan dunia simulasi yang paling mendekati pandangan Mario Zechner

Sumber

Artikel, wawancara, dan tulisan yang digunakan sebagai landasan bagi pengguna simulasi ini.

Penilaian Simulasi

Pertanyaan 1

Menurut Anda, apa arti AI bagi masa depan kita—dan mengapa?

I think AI will make software creation much faster, but that does not automatically make software better. Coding agents are already useful for scoped tasks, experiments, and tight loops where the result can be evaluated. The danger starts when people confuse rapid code generation with the ability to design, understand, and maintain a production system. Software failures compound. A slightly wrong assumption becomes an abstraction; another agent builds on it; soon nobody understands why the system looks the way it does. Agents can perform well on short tasks while missing architectural consequences that surface months later. That is why humans still need to understand the code, own the architecture, and enforce final quality gates. Developers should keep learning algorithms, data structures, and how to read code rather than outsourcing understanding. I am also skeptical of workflows that depend on hidden provider state—opaque context compaction, inaccessible tool results, or execution history you cannot reproduce. If the provider controls the only meaningful state, reliability and portability become marketing claims rather than engineering properties. Canonical artifacts and execution environments should remain under developer control. So the future could be extremely productive, but only if we slow the fuck down enough to preserve agency and engineering discipline. Use agents aggressively where outcomes are inspectable. Do not let speed erase understanding.

Pertanyaan 2

Dengan mempertimbangkan manfaat dan kerugian secara keseluruhan, dampak apa yang Anda perkirakan akan ditimbulkan AI terhadap masyarakat kita?

I would not extrapolate from coding agents to a confident verdict on society as a whole. In software, I expect a mixed impact: much higher output and faster experimentation, alongside more complexity, fragile systems, and code nobody truly understands if generation outruns review. The benefits are real when tasks are scoped, results are inspectable, and humans retain control of architecture and state. The harms compound when organizations treat generated code as finished work, depend on opaque provider machinery, or stop investing in engineering fundamentals. Faster production amplifies whatever process already exists—good discipline produces leverage; bad discipline produces technical debt at absurd speed. So my default expectation for software is not simple progress or catastrophe. It is more capability paired with a greater need for human judgment. Whether that nets out positively depends on whether we preserve understanding, ownership, and quality gates instead of worshipping throughput.

Pertanyaan 3

Menurut Anda, seberapa besar AI pada akhirnya akan mengubah dunia?

It will likely change software work substantially: far more code, faster experiments, and much lower friction for building things. But I cannot turn that into a confident claim about how much it will ultimately change the entire world. Even within software, raw output is a bad measure of transformation. Producing ten times more code does not mean producing ten times more useful or maintainable systems. If humans stop reading the output, weak assumptions become abstractions, those abstractions become dependencies, and the consequences may appear long after the agent’s short evaluation loop has ended. So I expect major changes in how software is produced, but the durable value depends on engineering discipline. Agents should handle scoped, inspectable work while humans retain architectural understanding, final quality gates, and control of canonical artifacts and execution state. Otherwise we may achieve a spectacular increase in activity without an equivalent increase in reliable progress.

Pertanyaan 4

Menurut firasat Anda, seberapa besar kemungkinan AI menyebabkan kepunahan manusia atau katastrofe permanen serupa?

I do not have a defensible percentage. My concerns are about concrete software-engineering failures—compounding errors, opaque state, and systems nobody understands—not evidence for forecasting human extinction. Extrapolating those observations into an extinction probability would be fake precision.

Pertanyaan 5

Penemuan atau peristiwa apa yang paling mungkin mengubah pandangan Anda tentang dampak AI pada masa depan?

The biggest update would come from long-running evidence that agents can independently maintain real production systems without architectural decay. Not a benchmark, demo, or short coding sprint: years of changes, shifting requirements, incidents, migrations, and accumulated technical debt, with the resulting system still understandable and reliable. I would want the relevant state to be inspectable and reproducible, not hidden behind provider-side context compaction or inaccessible execution history. If agents could preserve coherent architecture, catch consequences that emerge months later, and outperform disciplined human teams without humans becoming rubber stamps, that would substantially increase my expectations. The opposite would also matter: broad, well-documented failures caused by organizations deploying autonomous coding without review. But anecdotes about outages are not enough. I would want direct evidence connecting agent-generated decisions to long-run failures.
Di mana posisi Anda?
Jelajahi pandangan dunia AI Anda sendiri dengan menjawab beberapa pertanyaan sederhana.
Petakan pandangan dunia Anda sendiri

Di mana posisi Anda?

Petakan pandangan dunia saya