HackerTrans
トップ新着トレンドコメント過去質問紹介求人

mbellotti

no profile record

投稿

Hacking Your Software Performance Review

bellmar.medium.com
3 ポイント·投稿者 mbellotti·2 年前·0 コメント

Three questions to turn the table during technical interviews

bellmar.medium.com
164 ポイント·投稿者 mbellotti·2 年前·109 コメント

Intelligence (artificial or otherwise) Might Not Exist

bellmar.medium.com
2 ポイント·投稿者 mbellotti·2 年前·1 コメント

I'm annotating important social science papers for technical audiences

techshouldknow.com
2 ポイント·投稿者 mbellotti·2 年前·0 コメント

How to Program in Your Sleep

bellmar.medium.com
99 ポイント·投稿者 mbellotti·3 年前·50 コメント

The First Thing We Do, Let’s Kill All the Consultants

bellmar.medium.com
2 ポイント·投稿者 mbellotti·3 年前·0 コメント

The Challenge of Regulating AI

blog.rebelliondefense.com
1 ポイント·投稿者 mbellotti·3 年前·0 コメント

Come Break My Compiler

bellmar.medium.com
116 ポイント·投稿者 mbellotti·3 年前·32 コメント

Analog computing may be coming back

bellmar.medium.com
99 ポイント·投稿者 mbellotti·3 年前·84 コメント

Stop Using “Real Time” Wrong

bellmar.medium.com
35 ポイント·投稿者 mbellotti·4 年前·21 コメント

Why Self Driving Cars Are Not Safe

medium.com
2 ポイント·投稿者 mbellotti·4 年前·0 コメント

Computer science is a liberal arts degree

bellmar.medium.com
92 ポイント·投稿者 mbellotti·4 年前·146 コメント

Five Koans of Software Architecture

bellmar.medium.com
25 ポイント·投稿者 mbellotti·4 年前·14 コメント

Can You Use Formal Verification on a TableTop Game?

bellmar.medium.com
2 ポイント·投稿者 mbellotti·4 年前·0 コメント

The deification of Alan Turing

bellmar.medium.com
67 ポイント·投稿者 mbellotti·4 年前·36 コメント

The Death of Process

bellmar.medium.com
163 ポイント·投稿者 mbellotti·4 年前·48 コメント

The Unreasonableness of Math Is Context Independence

bellmar.medium.com
76 ポイント·投稿者 mbellotti·4 年前·46 コメント

Work Somewhere Dysfunctional

bellmar.medium.com
110 ポイント·投稿者 mbellotti·4 年前·80 コメント

Dockerizing a Programming Language

bellmar.medium.com
56 ポイント·投稿者 mbellotti·5 年前·15 コメント

Hunting Tech Debt via Org Charts

bellmar.medium.com
250 ポイント·投稿者 mbellotti·5 年前·87 コメント

コメント

mbellotti
·5 か月前·議論
I'm probably too late to the party for this comment to matter but: what the AI community pushes as "Safety" isn't actually Safety. Read Sidney Dekker. Read Nancy Leveson. Read Jens Rasmussen. Safety is not building perfect technology that never makes a mistake.

When I was working in defense technology I had two questions for engineers when we talked about Safety:

1) Can the operator assess the risk of using this technology? 2) If something goes wrong during operations, can the operator mitigate the risk?

The degree to which either of those statements is true is a measure of how safe that technology is. Technology that is simple to understand and executes deterministically every single time and where it is obvious if it is malfunctioning and the operator has enough time to either correct it or stop it, is generally perceived as safe. Technology that hides what it is really doing, confuses the operator about what the effects of operating it might be, and either executes faster than the operator can respond or specifically prevents the operator from responding, is more likely to trigger negative safety outcomes.

The problem the AI industry faces is that tricking the operator into thinking the technology is doing something it is not is explicitly part of their business model. Read any of the mentioned authors (Dekker is probably the best starting point) and it will become obvious why AI Safety is impossible when AI is dependent on pretending to "think" and "reason". In order to be safe they would have to abandon that. If they abandon that, they will be unable to raise the capital they need to keep the bubble from bursting. The technology will survive, maybe with another AI winter, but many of the businesses will not.

So they will abandon the lip service about Safety instead, but then that was never real Safety to begin with. Real Safety is not about zero risk. It is just as impossible to have zero risk as it is to have 100% uptime. Real Safety is about how the technology is designed to manage risk as part of an overall system.