Skip to content

2 min read

tl;dr in tech - Issue #86

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

On this page
  1. Simple Explanations For Complex Phenomena
  2. Getting More From Your Team Health Checks
  3. The Case Against Relying Solely On DRY
  4. Online Gradient Descent Written In SQL
  5. How Virtual Environments Work
  6. Why Some GitHub Labels Illegible
  7. SQL Translator

By: Paulo André

tl;dr: Paulo highlights the conflict between engineers’ desire for certainty and order, and the ever-changing scope of their work. He suggests a “momentous shift in mindset” to approach work with “less predicting & planning, more probing, sensing & responding.” A great read for software engineers dealing with complex, unknown requirements.

By: Justin Kotzé, Fiona Siseman

tl;dr: Spotify leaders use team health checks as a data source to support, not judge, their teams. The checks follow a pattern of predefined questions, debrief workshops, and aggregated visualizations to observe patterns and trends.

By: Ashley Peacock

tl;dr: Ashley Peacock argues that the DRY (Don’t Repeat Yourself) principle can be overused, leading to worse code in the long run. Duplication is not always evil, and sometimes it’s okay to repeat yourself. A thought-provoking read for software engineers aiming to balance code quality and reusability.

By: Max Halford

tl;dr: Max Halford explores implementing the Online Gradient Descent ML algorithm within a relational database using SQL. Training the model directly in the database can eliminate the need for separate inference/training services.

By: Brett Cannon

tl;dr: Brett Cannon explains the two parts of virtual environments: directories and configuration files. He uses the example of creating a virtual environment in a Unix-based OS. A useful guide for software engineers looking to understand the inner workings of virtual environments.

By: Moritz Firsching

tl;dr: Moritz Firsching explains the issues with GitHub’s label color selection for pull requests and issues. The text color on labels depends on the brightness of the label color, leading to illegible combinations.

tl;dr: The SQL and Natural Language Translator is a free, open-source tool designed to translate SQL commands into natural language and vice versa. It helps non-experts understand and write SQL queries without needing deep technical knowledge.

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 at his desk, chin on hand, with a microphone in front of him

Joe
Karlsson

I write about my homelab, AI tools, databases, and the weird stuff I build on the side.

More about me →

BlueskyLinkedInGitHub