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

tl;dr in tech - Issue #1

tl;dr: Lenny’s framework for giving performance reviews, starts with how to prepare:

1) Gather direct feedback from your report & their coworkers.

2) Capture accomplishments.

3) Describe their “superpower.”

4) Write a short high-level summary of their performance.

5) Identify 1-2 development areas, with examples, concrete suggestions, and what success looks like.

6) Share a timeline for their next career milestone. Lenny also discusses how to deliver and follow-up the review.

tl;dr: “This is the fifth post in a multi-part series on how Netflix uses A/B tests to inform decisions and continuously innovate on our products.” This post covers helpful questions to ask when thinking through if a test is conclusive enough.

tl;dr: What companies do not consider when demanding that senior engineers know specific technologies:

1) Most of the job is unrelated to that technology e.g. databases, deployment, mentoring.

2) Experienced engineers can pick up new technologies relatively quickly.

3) You may not be using this technology in perpetuity. And more.

tl;dr: Gergely looks at 30+ compensation related data points to see how companies, across different regions, are adjusting to the rapidly changing hiring market. His advice: “if your company has not yet made off-cycle compensation changes, you’ll likely have to make a case for a larger than usual raise for the new year. Start engaging your leadership now.”

tl;dr: “This article is not an attempt to explain containers in one go. Instead, it’s a front-page for my multi-year study of the domain. It outlines the said learning path and then walks you through it, pointing to more in-depth write-ups on this same blog.”

tl;dr: “We started, like we often do, with git bisect. It helped us track down the set of changes that appeared to have introduced the issue; adding a Dark Mode to Tines. “This is bizarre,” we thought, “how could a bunch of CSS changes have slowed things down?”.”

tl;dr: “Lambda is split into a control plane and data plane. Each plane is responsible for a specific set of activities in the service. The Control Plane provides management APIs and manages integrations with all AWS services. Whilst the Data Plane is Lambda’s Invoke API that triggers Lambda function invocations, this explanation is still very abstract but things will become clearer over time.” Bruno details the underlying mechanics of AWS Lamda.

tl;dr: A complete CS study plan to become a software engineer.

tl;dr: “JSON is a popular data format today and can be extremely useful for applications that need to capture information about objects that may vary in their attributes.” Akmal describes the multi-model capabilities of SingleStore by focussing on JSON data.

Videos