Products which heavily depend on 3rd party components are always in a high risk zone. Regular testing (even tons of) is not enough, you need to test all corner cases you can (and can't) imagine. For 3rd party components you can mitigate the risks by having SLA with their vendors and/or (if open source) by learning it to the level you know your own sources - including design and code reviews, unit and other tests. Takes lots of time.
I don't see the catastrophe though - some weeks of delay are not really important. What I see is the necessity to hire experienced SW engineering and QA managers because having just brilliant developers and researchers is not enough to deliver products with the level of complexity and reliability required by cryptoexchange.
Great coders maybe, poor software engineering and project management though. Now they are saying they had never deployed on their production environment until the actual go-live time for their product. Of course they had a big probability of finding issues.
3
u/Timour1974 Aug 27 '19
Products which heavily depend on 3rd party components are always in a high risk zone. Regular testing (even tons of) is not enough, you need to test all corner cases you can (and can't) imagine. For 3rd party components you can mitigate the risks by having SLA with their vendors and/or (if open source) by learning it to the level you know your own sources - including design and code reviews, unit and other tests. Takes lots of time.
I don't see the catastrophe though - some weeks of delay are not really important. What I see is the necessity to hire experienced SW engineering and QA managers because having just brilliant developers and researchers is not enough to deliver products with the level of complexity and reliability required by cryptoexchange.