/Career Advice

Analysis Of Compensation, Level, And Experience Details Of 19k Tech Workers

- Chip Huyen tl;dr: Chip ran an analysis to attempt to answer several questions including "how long does it take for software engineers to reach a certain level?" and "do women get paid less than men in tech?"

featured in #171

Good Businesses Have Margins

- Justin Jackson tl;dr: Justin advises entrepreneurs to optimize for margin - both business margins such as profit and personal margins, by creating boundaries for yourself. 

featured in #171

Your First 90 Days As CTO Or VP Engineering

- Will Larson tl;dr: Covers the following areas - priorities and goals, making the right system changes, tasks for the first 90 days, learning and building trust, building a support system, organizational health and process, hiring, execution & technology. 

featured in #170

The Myth Of Architect As Chess Master

- Ben Northrop tl;dr: While the rules of chess are consistent, the rules of software are not. To be an architect, you need to understand the specific "game you're in" - the business drivers, risks, technical constraints, integrations, trade-offs, and so on. 

featured in #170

Goodbye, Clean Code

- Dan Abramov tl;dr: Developers strive for cleaner code. There's an inflection point when a developer starts writing code in abstraction, this feels like a "super power." Dan learnt this comes with its own trade-offs. "Clean code is not a goal."

featured in #169

It's Time To Start Writing

- Alex Nixon tl;dr: Alex highlights the merits of writing a short memo to consider internal decisions. Writing a memo - as opposed to a presentation - makes the author think much more clearly and concisely about the issues at hand.

featured in #167

What Happens When Your Career Becomes Your Whole Identity

- Janna Koretz tl;dr: “Enmeshment” is where the boundaries between people become blurred, and individual identities lose importance. You can become enmeshed with your career too. This article discusses why this happens, the dangers and what you can do. 

featured in #167

The Lesson To Unlearn

- Paul Graham tl;dr: "Schools train us to win by hacking bad tests" so we can get good grades, but not learn. Good grades reward us in obvious ways. This mindset filters into the startup world, founders want to hack the system. This is correcting itself and that makes Paul optimistic.

featured in #165

Inefficient Efficiency

- Kent Beck tl;dr: Latency is “the time interval between a stimulus and its response." Throughput is “the rate at which a system achieves its goal”. Kent discusses the relationship of these two in architectural decisions, and when to optimize which. Click the link in this tweet if you're paywalled.

featured in #164

A Comment Is An Invitation For Refactoring

- Gergely Orosz tl;dr: A comment is usually a sign that a piece of code needs refactoring. Greg wants us to ask "could I refactor the code to remove this comment?" The answer is typically yes. He highlights three common examples of comments.

featured in #164