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

swimming pool with stainless steel ladder

Photo by Etienne Girardet on Unsplash

I’d like to introduce you all to my friend and coworker, Bailey Hayes, Principal Software Engineer here at SingleStore.

tl;dr: “This is the story of CVE-2022-0847, a vulnerability in the Linux kernel since 5.8 which allows overwriting data in arbitrary read-only files. This leads to privilege escalation because unprivileged processes can inject code into root processes.”

tl;dr: “This is an upcoming high performance computing book. Its intended audience is everyone from performance engineers and practical algorithm researchers to undergraduate computer science students who have just finished an advanced algorithms course and want to learn more practical ways to speed up a program.”

tl;dr: Coinbase’s Director of Eng:

1) Shape your org chart so your product reflects what you want to ship.

2) Push part of the strategic decision-making process down the org to gain speed and flexibility.

3) Think in 3D to visualize what’s missing i.e, think about how the work gets done, not just who does it.

4) Put people over org structures and leverage emerging leaders.

tl;dr: “Trying to generalize across many problems is a fraught endeavor. What’s better is getting to know a specific problem by working collaboratively and embedding with the people who have the most tacit knowledge of the problem.”

tl;dr: “Today we’ll look at how 3 high performance engineering companies handle their technical documentation” starting with Google and their g3docs system, which “made documentation radically simpler for engineers.” It

1) presented one way to document things, removing decisions.

2) Hosted docs next to the code so engineers can stay in their IDE.

3) Automatically rendered docs into designed HTML pages on commits.

tl;dr: “There is so much to learn, to experiment with, to experience. There are thousands of languages out there, each with their own story to tell, and their own way of telling that story. We should never settle for just one language or one way of doing something, because new languages and new approaches change how we view the world.”

tl;dr: “Here are a few examples of small personal programming projects I’ve done. I’m not going to talk about “learning projects” where my goal was to learn something specific because I’ve already written a billion blog posts about that. These are more about just doing something fun with no specific learning goal.”

tl;dr: “An open-source initiative that subjects popular web browsers to a suite of automated tests. These tests are designed to audit web browsers’ privacy properties in an unbiased manner. The results of the tests are made public to help users make an informed choice about which browser to use, and to encourage browser makers to fix leaks of private user data.”