edgecase_datafeed 108 2019-05-03 This is the date at the time of creation of this datafeed article. A checkpoint article containing a hash of this datafeed article may be created on this date or at a later date. 106 8 2019-04-27 bitcoin cd3f7f4c5d2b44dd03ad0ad59109376aaabe13d81acdac1700d374086fc920c0 573429 1HtwyqFWNVDoSEVqZwjBRRAV2oEsi8aQXr 16awNgyNAoqjhVjenPGZY8QZtKQKHgzwJa
Conversation:_Programmer_Licences stjohn_piano 2019-05-03 yes Nicholas Piano: Off topic: medical students must dissect a whole cadaver to get their licence. What would be similar for programmer licence? StJohn Piano: Implementing an API on a server? Complete with automated deployment. Nicholas Piano: It needs to be something that proves someone's worth beyond a doubt. Imagine we treated programmer failure like the death of a patient in surgery. Think of a system tested so completely that every possible use case has been accounted for. Perhaps an air traffic control simulation or a bookkeeping task Like the Kobayashi Maru StJohn Piano: Yeah Hm. Don't know. Can't do it perfectly. We don't understand the body perfectly. But could do it very well indeed, yes. Can't have "beyond doubt" but could have "beyond even very unreasonable doubt". Nicholas Piano: Consider: medical students start for two reasons; high pay and desire to help people. These are both very visceral motivations. You cannot have programmer licensing without a drive as strong as this. People became airborne rangers in the US army during WW2 because of slightly higher pay StJohn Piano: yes didn't know that about rangers. ha. hm ok, how about this: q: why are medical licences helpful? a: because patients, hospitals, insurers etc want to see them, or at least know that they exist and can be verified. because people are quite sensitive about their survival up to now, software (outside of e.g. air traffic control, trains) has not been critical to survival sony etc lose customer data all the time. no one cares. no one stops using them. speed of deployment and time to market has mattered most for the last generation (or more) in software "generation" here refers to a human generation. I am using "speed of deployment" to refer to "speed of deployment of new features", whereas "time to market" is "time taken to get minimum viable product to market". These should probably be the other way around. I should also add "compatibility with existing software and hardware" - this has consistently been a winning characteristic for 40+ years, I think. and then growth, until ideally you crack the world with your weight (e.g. microsoft) this approach necessarily involves a lot of leakage, both of money and of personal information, and of control of user accounts. (convenience necessarily trades off against security) now, post-bitcoin, something changed. money can be scarce This should be "scarce again". It's been scarce before. Consider the effort people used to go to in order to move gold around: article John_T._Flynn:_How_the_great_Rothschild_family_of_bankers_got_started edgecase 35 John T. Flynn: How the great Rothschild family of bankers got started mistakes with code that handles user account access (i.e. identity) and with code that handles money can hurt. really hurt. because the damage cannot be printed away and pain makes people sensitive to risk. so I think we'll get programming licences because those who purchase programming time now have a reason to care about programmer quality much more than they used to. Not just quality, but also a reputation for trustworthiness. this applies even if bitcoin dies, etc etc, and is replaced by 5 variants. the pain will still exist, perhaps in a more diluted form, but it will still be present, more so than in pounds or dollars. obviously this will take a while. it'll happen first wherever software systems are interfacing with bitcoin. or are under pressure from ransomware. wherever it hurts the most. StJohn Piano: ^ mind if I publish this convo? starting from "medical students must dissect a whole cadaver to get their licence." Nicholas Piano: Yes, no problem StJohn Piano: Want to be anonymised, or happy to have your name in print? Nicholas Piano: Name is fine StJohn Piano: Cool Chat transcript edited slightly for readability.
iQIcBAABCgAGBQJczG1JAAoJEC8RP+HmG9MX9YUP/3cqkW+G7JdimqrMfOJoQRgf PqnJ8obJVixAhA6eWCDiFdeAVfqNBR2CCOvDet8+RkU7H4QK+oaZWOyx2qkcAvn5 QWjSOIReKpFqR4CHsuNtw6gL7Da927SX2SWIyg4y+joAFuCHRBiCIFyp73PvkElZ LerT1dThH36ebyrdliN6eH8AUs6TuJ1gIqG6yMMQ/v8cXm4jlH/FfGA5ZURGVTid xCmW1ERgmHYaoJRSqjB2CmCBYHfDwCzap9dQ4QjJuJlbaZlp7Cve98WBQ5UONCv0 JmsgJEjXyDZ/0Z1YfvcLjbDnl5aywUFNsd8Zl6HClXHLd5QlKBRfG8T5BB6rdEY0 RktfUT4bfiyHNtHj5s48WiYRasJV/kYEws0tuwuup/JffP8aNPlNs1T/JfrnUN2x ekQe/REauu0nOhCdWhd3w7pC7svlrK7MFTHyXlLUD44LOmTe7IZPckocG1XClW4R KQYCQUqMFNVEeSPLq808jraU/+SfxhtfA3T6W40oE2dMl6e4SvBZvXF1ksnI6CdV +r+8Bxqd6AGS00W01g/6BFT6rZGr94lrxp9JoISQ+b6mYI4Nyb8Tz5uMDQsBVZn9 lVMGYWntJfI9Fbw0M8LJTdCA0Y5XoLJG5ctKGXJ55pIJNxXMPmB9GjKe+1AfEkY9 4AlAxIXp4ROkX4mb3wQK =OXbi
iQIcBAABCgAGBQJczG2BAAoJECL1OzZgiBhwwNgP+wexym2QlJF5kYOxfj42Kx+Z WQwumwTbP5bL6By677QIwe2YqxsqI53GpUcRGFktjs5/NEKgVBa0/ixcdKiyVZSz le9GVJ9SA1HYjPxuFSLsYB6bmhLWhodLxxPHrBdxIO1yFp2sfChjJ4+HJ02eErn6 IzHPLAl2z98c+4mq86LdDXhM5Pxg9emRHIV2Dh3lkTLCiMUt4tcUh25DqI1ZZ6fK qc6wIAQqO7x4biQBqgM+OPPwM/8fUFaeBYVz3rI/hHikRuIDgX8XPQ1whR67G54X c43ZbhMQx6TpwUpWLyPFM1rDm6+cbkoLln7n9FSIQ4pAW24+1Lhc6T3En8hSrJ4p CHttUfm3+xJgk6E1tBOTFRgYfVjZzEjM1k7HnFWmUAoD6P2ZNoxMXYzDLsuyUJVH 70A9LXCy5thL4w/LDK4m9AvvBXMZZjaMlsNvgMsCu7cYfbA50czlJAC77SXbb9PG GQuv/5J/CssaY5B51P7SDVNa7wFaUn7iuFohB/FkzF+1vggs6s/AU4XsrGLkYGgn 1FyWTbgz8edekSX6w/bIgAdpAxGpH5Yrz0DXn8IuHN1uNSp86/A31wzxj5uYq6Q+ DwXgVYdZQWxyqb3khe/fdqre6jLMaedoYyEG5s+myGeco7viiO4t9bbxrpxE7jBy AWu83JxJAo7s83YdXcpO =oPdb