Florian Herlings.

This was sent out as a newsletter on 11. October 2019. Please feel free to sign up to get future updates delivered to your inbox automatically.

Lies, Kubernetes, code cartoons and more…


Hello there,

welcome to this week’s edition of the newsletter. I started a new job this week so this will be slightly shorter. I am still very open for any kind of comment or input via twitter/__florian.

The biggest lie tech people tell themselves — and the rest of us” by Rose Eveleth

We as technologist play a central role to how the world is shaped and what our future will be. This article challenges some of the world views many of us in technology share.

Technologists’ desire to make a parallel to evolution is flawed at its very foundation. Evolution is driven by random mutation — mistakes, not plans. (And while some inventions may indeed be the result of mishaps, the decision of a company to patent, produce, and market those inventions is not.) Evolution doesn’t have meetings about the market, the environment, the customer base. Evolution doesn’t patent things or do focus groups. Evolution doesn’t spend millions of dollars lobbying Congress to ensure that its plans go unfettered.

Learn Kubernetes with this 5 part series” by Chris Noring

In the second edition of this newsletter, I already linked to a series of great articles that teach you how to use Kubernetes. This five part series is similar, but has a lot more context and gives a deeper insight into the “why” of Kubernetes. To me, containerization is such a big topic, that I dare to link this series as well. :)

WebAssembly Interface Types: Interoperate with All the Things!” by Lin Clark

Lin Clark has a full series of awesome code cartoons on the mozilla website. The latest cartoon is about how web assembly types can be used to help interoperability even beyond WASM on the web.

RFC driven development” by Pedro Pereira Santos

What if we were to actually think through some of the implications of an implementation and document it, before we actually started to work on the details? Well, RFC driven development suggest that we do that. It is an interesting thought, and I have seen this kind of process here and there, when very big decisions had to be made. At least in my experience, it always yielded a great result and was the starting point for great discussions.

So, that’s it for this week. Thank you for reading and have a wonderful day, Florian


I do not use any tracking or feedback mechanism on this website. Instead, I would love for you to get in touch with me via twitter.com/__florian to let me know if you liked it or if you have any suggestions or questions.