In my experience, programmers totally overlook costs due to "buying the coffee company to make a cup of coffee"
Think this is true not just for dependencies, but also for changing the standard approach of doing something. There are many hidden costs beyond the benefits of the switch. For example, there may be the time cost of all devs on project having to learn the new approach.
Good Dalio talk on having an idea meritocracy:
"Rules can aid the wise, but they are snares to the fool" https://www.jstor.org/stable/45104797
Always been fascinated by this:
Managed to follow some Mastadon people - very nice
Good article on scheduling
Disappearing down a concurrency rabbithole... 📄.pdf #programming
Talk on concurrency patterns in golang:
When programmers start praising code, I start to think something horrible has happened #programming