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 #9

tl;dr: “The goal of this post is to help remind you to reflect on your current development process. Is there some piece of your pipeline taking longer than it needs to? Is there a way to create some debug tools that makes it easier to test a change? Would unit testing bring benefits, but you keep avoiding it because you think there’s a big upfront cost to it?”

tl;dr: “At Twitter, most CPU bound services start falling over at around 50% reserved container CPU utilization and almost all services start falling over at not much more CPU utilization even though CPU bound services should, theoretically, be able to get higher CPU utilizations.” This document describes potential solutions.

tl;dr: This article gives an overview of engineering milestones that will happen in 2022. The technologies include Wi-Fi 6E, electric planes, 3-nanometer chips, cryogenic energy storage, and more.

tl;dr: “This year in review is a no-nonsense write-up of some great things that happened, a bit of drama, and some things we did poorly… We figured we could use SingleStore for everything, and that’s what we did. This move saved us a huge chunk of cash.”

tl;dr: “This article explicitly focuses on senior leadership roles, which were what I was looking for.”

1) It will likely take longer than you expect.

2) Independent headhunters and recruiters are a valuable resource.

3) Use your project management skills to keep your sanity.

4) Be strategic around your interviews and chats.

5) Do not waste your time, but part as friends with everyone in the process.

tl;dr: Mentorship conversations are quite different from coaching conversations. “When someone comes to me, they’re usually asking bigger question not tied to our day-to-day work and these conversations fall into three categories:”

1) Goals - figuring out what they really want.

2) Situations - handling the unfamiliar or difficult.

3) Skills - getting promoted. David discusses how to mentor each.

tl;dr: Candost sees decision-making as a spectrum - or pendulum - between authority and consensus: “On one side, we have the authority, and on the other side, we have the consensus. This pendulum requires leaders to go back and forth. Having flexibility in decision-making is crucial and more persuasive than sticking to only one.”

tl;dr: “How Liberty Mutual implemented a high-performing DevOps culture to increase stability, shorten release cycles, and deliver value faster.”

tl;dr: “The prospect for another federated, Internet wide communication system seem very remote at this point in time, so email is it.” Email is our only reliable communication method between different organizations and, at this point, companies have something to lose if companies try to replace email.

tl;dr: Laws, Theories, Principles and Patterns that developers will find useful.