1. autonomous "sociopathic" code = bad 2. preventing private interests from monopolization = bad 3. governance of blockchain as a public utility = good 4. reinventing political philosophy & definition governance in a couple blog posts = ambitious but fraught.https://twitter.com/VladZamfir/status/1048041294407356416 …
-
-
Those were examples; actual terminology I guess would be: 'service outage', 'service interruption', or 'incident'; with 'post-mortem' being common term for retrospective to determine root cause of outage after the fact. Post-mortem would describe incident in more specific terms.
-
Thanks man, had to Google half of those examples, but I get it now. It's a nightmare.
End of conversation
New conversation
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
There's no fear quite like the fear you feel when your code becomes 'accidentally autonomous'.
(This isn't really the terminology we use when it happens, but it's absolutely a thing that happens. Gulp.)