tl;dr in tech - Issue #77
From the TL;DR in Tech archive, originally sent on Substack. Some links may have died since.
On this page
- Setting Engineering Org Values
- Corporate Legibility for Software Engineers
- Start Coding At The Point Of Least Certainty
- Numbers To Know For Managing (Software Teams)
- Pull The Andon Cord
- Automating Safe, Hands-Off Deployments
- Tag Systems
- Python’s “Disappointing” Superpowers
- Rust’s Ugly Syntax
- Various Ways Of Sending Mail Via SMTP
tl;dr: Will tackles the great engineering org value debate like a pro, answering the big questions and sharing his secrets to success. Discover how to create a values-based engineering team that’s more powerful than a mustang in full gallop! 🐴
tl;dr: “Corporate legibility is the art of making tasks, and their outcomes, easier to understand for those not directly involved.” Matt shows you how to become a corporate legibility master and boost your career faster than a tumbleweed in a windstorm. 🌪️
tl;dr: Swizec reminds us that “you know you can get a monkey” but challenges us to think about whether we can “train the monkey to jump through the hoop?” Don’t just code the easy parts, partners - tackle the tough stuff head-on! 🐒
By: Unknown
tl;dr: The authors provide a list of numbers for managing software teams, covering topics like minimum number of direct reports, candidates to interview before deciding, days before a new hire should merge a pull request, and days before a small support issue becomes a large one.
By: Taylor Pearson
tl;dr: Taylor Pearson discusses Toyota’s Andon Cord, which could halt the assembly line when pulled by a worker who spotted an issue. The worker then had to propose a solution. This process had two benefits: (1) it made workers feel trusted and involved, and (2) it increased quality by tapping into workers’ tacit knowledge.
By: Clare Liguori
tl;dr: Clare Liguori outlines the steps a code change goes through in an Amazon pipeline on its way to production, detailing the four major phases: source, build, test, and production. It’s a good look at how a typical AWS service team might set up a continuous delivery pipeline.
tl;dr: Daniel throws caution to the wind and shares his “non-comprehensive, poorly-researched thoughts on tag systems.” It’s like a wild west saloon chat about tag systems without worrying about the nitty-gritty. 🍻
tl;dr: Luke laments the potential loss of Python’s dynamic features, fearing a future where Python is just another C# or Java. Don’t let Python’s superpowers go to waste, folks! 💥
tl;dr: Alex boldly claims that “most of the time when people think they have an issue with Rust’s syntax, they actually object to Rust’s semantics.” Dive into this mind-bending exploration of syntax vs. semantics and emerge a Rust aficionado. 🦀
tl;dr: Charles proves that SMTP ain’t all that bad, showing us how to send emails with minimal fuss. It’s like having your own personal Pony Express rider delivering your messages! 💌
Works on My Machine
Get the next issue by email. It covers homelab builds, AI tools and open source, and it goes out when I have something to say.
It’s free, and you can unsubscribe anytime. You’ll get an email to confirm first.
If you liked this issue, consider sharing it on Hacker News, Bluesky, LinkedIn, or X.

Joe
Karlsson
I write about my homelab, AI tools, databases, and the weird stuff I build on the side.
More about me →