Skip to content

2 min read

tl;dr in tech - Issue #79

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

On this page
  1. Ordering Numbers, How Hard Can It Be?
  2. Contracts You Should Never Sign
  3. What We Look For In A Resume
  4. 30-60 Days In A New Leadership Role: Run Experiments For Change
  5. Cursor
  6. Diagram Layout Engines: Minimizing Hierarchical Edge Crossings
  7. A Charming Algorithm for Count-Distinct
  8. Accelerating Our A/B Experiments With Machine Learning

By: Orson Peters

tl;dr: Ordering numbers may seem like an easy task, but it can be quite challenging. Even with explicit instructions and guidelines, it is difficult to get it right on the first try. The Python standard library even states that “comparison is pretty much a nightmare.”

By: Vadim Kravcenko

tl;dr: As a software engineer, there are certain contracts you should avoid signing. These include non-compete clauses in employee contracts, confidentiality agreements, exclusive distribution agreements, and project-based agreements without a clear definition of scope and definition of done. It’s important to understand the terms and conditions of any contract before signing it, and to be aware of potential red flags that could negatively impact your career.

By: Chip Huyen

tl;dr: When reviewing software engineering resumes, it’s important to look for demonstrated expertise, initiative and persistence, unique perspectives, and impact rather than meaningless metrics. As a hiring manager, it’s important to understand that keywords don’t necessarily indicate expertise, and to look for evidence of successful projects and meaningful contributions.

By: Lara Hogan

tl;dr: When starting a new leadership role, it’s important to run experiments to gather data and make informed decisions. However, it’s important to limit the number of experiments to avoid overwhelming employees, and to limit the timeline to 2-3 weeks. It’s also important to develop a communication plan and prepare to share the results of the experiments with the team.

By: Unknown

tl;dr: Cursor is an editor specifically designed for programming with AI. It could be an interesting tool if you want to experiment with AI-assisted coding.

By: Júlio César Batista

tl;dr: TALA is a new layout engine designed for software architecture that combines various graph visualization algorithms to produce aesthetic diagrams. In this article, the author discusses the inner workings of TALA and how it minimizes edge crossings in hierarchical layouts.

By: Justin Jaffray

tl;dr: Count-distinct is a common problem in software engineering, and this article presents a charming algorithm to estimate the number of distinct elements in a stream.

By: Michael Wilson

tl;dr: Dropbox uses A/B experiments to compare product versions and understand what works best for their users. However, analyzing these experiments can be complex, especially for a subscription-based model. This article discusses how Dropbox uses machine learning to accelerate their A/B experiments and improve

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