Links 19-02-16


Dev

  • The future of computing is analog – In this excerpt from his chapter “The Third Law,” George Dyson, a historian of science and technology, argues:

    We worry too much about machine intelligence and not enough about self-reproduction, communication, and control. The next revolution in computing will be signaled by the rise of analog systems over which digital programming no longer has control. Nature’s response to those who believe they can build machines to control everything will be to allow them to build a machine that controls them instead.

  • Programming paradigms for dummies – Adrian Colyer recently discussed “Programming paradigms for dummies: What every programmer should know” on his blog, The Morning Paper. See what he thought of this introduction to the main programming paradigms and read the full chapter here.

  • What’s new in Go in 2019 – You may have read that Golang is the highest-paying skill in the US. At The New Stack, David Cassel interviews Steve Francia, Google’s product lead for Go, about what’s in store for Go in 2019, including its new module system, error handling, Go 2, a revised proposal process, the importance of community to Go, and more.

  • Getting started with Google Colab – Google Colab is a free cloud service based on Jupyter notebooks that supports free GPU processing. Sound interesting? Anne Bonner leads a quick tutorial to get you up and running.

  • Basic Color Theory for Web Developers – how to make your website look good when you can’t even match your socks.

Ops

  • Monitoring Kubernetes and Docker – Sensu’s Sean Porter offers an introduction to monitoring Kubernetes and Docker. In part 1, he covers the rise of microservice architecture, using Kubernetes and Docker for container orchestration and management, and some of the challenges these new technologies present. In part 2, he dives into collecting Kubernetes data with Prometheus and the pros and cons of this approach.

  • How to create meaningful architectural diagram – “We try to create architectural diagrams (as part of the technical documentation) aiming to reflect the internal state of the application, but most of the time we do not do it properly.” Writing in InfoQ, Ionut Balosin explains what you’re likely doing wrong and how you can improve your architectural diagrams so that they support collaboration and communication and provide vision and guidance within your team and across teams.

tail -f/dev/newsletter

  • Travel back to a time when Fortran and COBOL were hip

  • Man, that Reddit’s a rock!

    – What’s the difference between a Syrian kindergarten and an ISIS hospital?

    – I wouldn’t know, I’m just the drone operator.

Copyright © 2017-2019 Stanislav Gobunov