From the TL;DR in Tech archive, originally sent on Substack. Some links may have died since.

tl;dr in tech by Joe Karlsson - Issue #16

tl;dr: “I enjoy collecting rare and vintage programming books. There’s just something quaint about pre-internet computer books, with their dead-tree print editions and crude typesetting.” Tiemo shares 3 favorites and sumarizes the backdrop of each.

tl;dr: “The proposal introduces a new operator. This operator is an idea borrowed from functional programming that makes applying functions more convenient in many cases. This post describes how the pipe operator works and what its use cases are (there are more than you might expect!).”

tl;dr: “I was curious to know if the functionality of VSCode can catch up with the native speed of some editors, such as Sublime. That led me to seek out where some bottlenecks may be and where time is being spent. In this post, I look at both the internals and extensions.”

tl;dr: “In this post I’ll run through a whistlestop tour of the concept of leadership, and share some of the prompts that I’ve used to help people navigate this tricky topic.” Sally provides us with 5 prompts to help us hone in on what our personal leadership style.

tl;dr: A company’s core values are important to consider when hiring but, how do you develop an interview question that measures those values? Jacob outlines 3 things:

1) Describe how the value influences action.

2) Figure out what behaviors are behind the value.

3) Find a situation where this value would influence behavior.

tl;dr: “What looks like a technical debt in a software solution, might be the most efficient way for people to deliver business value in a given situation. There is a beauty in that, if observed from a distance.”

tl;dr: “This post describes how the Netflix TVUI team implemented a robust strategy to quickly and easily detect performance anomalies before they are released - and often before they are even committed to the codebase.”

tl;dr: “Researchers from MIT, Purdue, and Yale demonstrated that turning off the camera during a Zoom meeting shrinks the environmental footprint by 96%.” This inspired Noah to think about a mobile app’s carbon footprint and he shows us how adding or removing 1MB in app size can have a surprisingly large impact.

tl;dr:

1) Hybrid working is here to stay but key questions remain e.g. how many days a week should we be in the office?

2) Companies that have been effective at developing loosely coupled systems - often with a microservices architecture - were better set up to work remotely and using a distributed approach.

3) Three interesting developments in the data engineering and AI/ML space in 2021, outlined here, and more.