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

tl;dr:

1) You don’t need hundreds of engineers to build a great product.

2) Simple Outperformed Smart.

3) Our highest impact findings would always come within the first and last few hours of the audit.

4) Writing secure software has gotten remarkably easier in the last 10 years.

5) All the really bad security vulnerabilities were obvious. And more.

tl;dr: “I offer the following argument that restarting from the initial state is a deeply principled technique for repairing a stateful system - whether that system is a program, or an entire computer, or a collection of computers.”

tl;dr: Nikolay covers 18 mistakes, categorized into three big categories of DB schema migration mistakes:

1) Concurrency-related mistakes.

2) Mistakes related to the correctness of steps.

3) Miscellaneous - mistakes related to the implementation of some specific database feature or the configuration of a particular database.”

tl;dr: The first version of Go has evolved significantly: The compiler rewrite in Go, modules, context package and Generics. “Releasing ‘Go 2’ has become a philosophical and political challenge due to the forces that be… This is a look back at the huge progress that has been made since Go 1 released and what I’d consider to be the headline features of Go 2.”

tl;dr: Broken into 5 categories:

1) Questions for gauging morale e.g. Who haven’t I heard from in my team?

2) Tracking team performance e.g. is each member on the team overperforming, on track or underperforming?

3) Measuring effectiveness as a manager e.g. What more can I say no to? And more.

tl;dr: “The following is a loose, unordered collection of thoughts that come up when I look back on the past 10 years:”

1) Fearlessness is undervalued.

2) You can’t predict the future; try and you might end up in trouble.

3) Nothing really matters, except bringing value to the customer.

4) Perfection is unachievable. And more.

tl;dr: Andreas discusses and addresses how we handle the 3 main issues when hiring remotely:

1) More people applying to job postings.

2) Team is in multiple locations.

gg3) Interviewing people with different cultural backgrounds.