1. 18
  1.  

  2. 3

    My favorite bit is towards the end where the author points on the differences in QA required for web vs. traditional software, and how that affects Ethereum smart-contract programming:

    Most programmers today are trained on the web development model. Unfortunately, the blockchain security model is more akin to the older model.

    In a lot of ways, we’ve gotten sloppy. Maybe this sort of thing will encourage us to get back to more rigorous testing and forethought.

    1. 1

      how that effects

      affects

      In a lot of ways, we’ve gotten sloppy.

      I wouldn’t blame web programming for that. If you were to make a public RPC API, would you allow the users to call any function in a third party library? That’s pretty much what they did with that multi-signature wallet code.

      1. 1

        Good catch, fixed typo. :)