> a Docker container for each line of code Yes, this is the surest way for developers to guarantee the code itself is always bug-free. Everything becomes "jus

> a Docker container for each line of code Yes, this is the surest way for developers to guarantee the code itself is always bug-free. Everything becomes "just an ops problem". 2017 predictions: buzzy job title: Ops-Dev. Labview-style graphical programming http://www.ni.com/newsletter/app/largeimage?lang=en&imageurl=%2Fcms%2Fimages%2Fdevzone%2Fpub%2Fnrjsxmfm912163998723206173.jpg http://www.ni.com/newsletter/app/largeimage?lang=en&imageurl... becomes the new hotness. Amazon and Google introduce new graphical programming workflow coordination services for lambda. Nothing ever gets finished. (2018 predictions: google discontinues this service) (2019 predictions: every machine instruction now belongs to its own docker package; the successor to Kubernates is marketed as a distributed asynchronous virtual CPU. Data centers begin requiring small nuclear stations to generate the electricity to power them. Still nothing gets finished). (2020 predictions: someone rediscovers this "heroku" thing; things start getting done again. Hot new industry: nuclear waste disposal) (2119 prediction: nuclear stations powering 2019's data centers are still running at full power but servers are all dormant; nobody wants to turn off a server "just in case").