Another recap of a week’s worth of links, news, and discussion around technical leadership and technology; as usual, follow me of Linkedin if you want to receive a notification when I share a new link.
What I read this week
This week I spent my daily 1.30h commute reading Kubernetes Up and Running, which is often recognized as the best introductory book on Kubernetes.
I actually tend to agree with the statement: it’s certainly a very good book, and an introductory one. Chapters 4–12 cover very well the basics of Kubernetes day to day use (kubectl, pods, services, replica sets, daemon sets, jobs, config maps, secret maps, and deployments), with many details and quite a few tricks I could use immediately at work.
The part on Kubernetes installation is (and couldn’t be otherwise, considering the width of the topic) minimal and outdated — the book was published in 2016, which is a long time ago. You won’t find advanced topics here: I’ll make sure to post in the future reviews of books you can use to learn more.
Topics I talked about this week
This week I posted (unusually) quite a few articles on Web and frontend technologies. First of all, observing that Thoughtworks is suggesting now to ADOPT Micro-frontends, I found two good introductory articles on them
I also learned more about browsers Reporting API thanks to Scott Helm presentation at the NDC Conference. Finally, I discovered more front-end application frameworks (as if we needed more) in the 2019 Comparison of Front-End Frameworks.
Having worked during the Big Data Craziness 10 years ago, I appreciated the AI Hierarchy of Needs. The article is a good reminder, for all the companies that are going all-in in AI and machine learning, that there’s a method, a process and a progression in entering Artificial Intelligence, and rushing it will not give you the expected return on investments.
Lately I’m appreciating more and more the idea of having immutable infrastructure and avoid to run as much as possible the use of configuration management tools at deploy time; I posted earlier a clever way to automate the creation of EC2 machine images.
A few more links to finish
- Cloud computing simplified: a Berkeley view on serverless computing
- Chaos engineering traps
- 12 Threat Modelling methods
- How to test Microservices with Consumer-Driven Contracts?
Have a great week!