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 …
-
Show this thread
-
-
I tend to agree that fully autonomous code is a really lousy idea
3 replies 0 retweets 8 likesShow this thread -
Replying to @stephendpalley
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.)1 reply 0 retweets 6 likes -
Replying to @arbedout @stephendpalley
What's the terminology you use when it happens?
1 reply 0 retweets 1 like -
Replying to @Dark_Realist @stephendpalley
شتر دیدی؟ ندیدی Retweeted شتر دیدی؟ ندیدی
شتر دیدی؟ ندیدی added,
شتر دیدی؟ ندیدی @arbedout'accidentally autonomous' code: A broken deployment across your server fleet that wedges SSH and/or Puppet An app update that manages to break the app updating mechanism A javascript bundle wedged in the cache of your CDN and stuck in client browsers despite your best efforts https://twitter.com/arbedout/status/1049430036686745600 …Show this thread1 reply 0 retweets 3 likes -
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.
1 reply 0 retweets 2 likes
Thanks man, had to Google half of those examples, but I get it now. It's a nightmare.
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.