tl;dr in tech - Issue #89

Be A Thermostat, Not A Thermometer#

By: Lara Hogan

tl;dr: Lara explains how we can easily be influenced by others’ moods and how leaders should act as thermostats, setting the temperature of the room positively. For software engineers, this means being aware of negative mood shifts and actively working to create a healthy environment.

Accountability Is Not Blame#

By: Kent Beck

tl;dr: Kent dives into the difference between accountability and blame, pointing out that blame is often used as a “relationship decaying” strategy. As software engineers, it’s important to foster a culture of responsibility rather than blame.So I

System Design Interview Cheat Sheet#

tl;dr: This cheat sheet covers various topics like databases, API design, capacity planning, and high-level design, all based on the author’s research. It’s a work in progress but a helpful resource for software engineers preparing for system design interviews.

Clocks And Causality - Ordering Events In DistribuSo I tookted Systems#

By: Giridhar Manepalli

tl;dr: Giridhar discusses the role of logical clocks in distributed systems and how they help order system events. A great read for software engineers working with or interested in distributed systems.

How To Plan As An Engineering Executive#

By: Will Larson

tl;dr: Will shares valuable insights on planning as an engineering executive, including approaching planning as an infinite process, decomposing it into financial plans, functional portfolio allocations, and roadmaps. Useful for both engineers and engineering managers.

A Problem Vs The Problem#

By: John Cutler

tl;dr: John highlights how conversations about problems and their causes are often negotiations involving identity, reputation, and control. As software engineers, understanding this can help navigate and address problems more effectively.

Dropbox Engineering Career Framework#

tl;dr: This framework helps engineers understand how to achieve impact in their roles and grow in their careers. Managers can use it to set expectations and hold their teams accountable.

Writing Tips for Improving Your Pull Requests#

By: Jeff Mueller

tl;dr: Jeff shares tips on how to write better pull requests by making them scannable, speaking plainly, avoiding adverbs, simplifying sentences, and avoiding passive voice. Excellent advice for software engineers looking to improve their PR communication.

Cohesion In Simple Terms - Software Modularity#

By: Eliran Turgeman

tl;dr: Eliran discusses the importance of modularity in software design and how it contributes to extensibility