Moving Fast with Software Verification | the morning paper
blog.acolyer.org/2015/11/20/moving-fast-with-software-verification
From the page
Saved with the link. Notes from 2007 to 2016 are mostly the page's own words, so this is probably an excerpt.
How do you mesh formal verification “proponents of which sometimes even used to argue that programs should be developed only after a prior specifications had been written down,” with a continuous delivery model? This strikes me as very similar to the problem of integrating security into a continuous delivery pipeline too. On the web, Facebook pushes new changes to code twice a day – but mobile platforms are now even more important than the web. With the mobile platforms (iOS and Android), you can’t just push new features and bug fixes the minute they are ready – Facebook can only distribute a new version to the Apple App Store or Google Play but the user controls if/when they update.
Same host · 5 links from blog.acolyer.org
- Experience with Rules-Based Programming for Distributed Concurrent Fault-Tolerant Code
- The design and implementation of modern column-oriented database systems | the morning paper
- File systems unfit as distributed storage backends: lessons from ten years of Ceph evolution – the morning paper
- Meaningful availability – the morning paper