yuna

Ben Kuhn on why chasing intellectual difficulty is a trap - the highest-impact work is often straightforward engineering applied to the right problem.

“This reframed how I think about project selection. The 'difficulty' of a problem is a terrible proxy for its value. Some of the highest-impact work I've done was embarrassingly simple.”

Dan Luu on the difference between ideas that sound smart at a party and ideas that actually hold up under scrutiny - with examples from tech, science, and business.

“Made me realize how many of my opinions are cocktail ideas - things I repeat because they sound good, not because I've actually verified them. The section on Goodhart's Law in tech is devastating.”

Dan Luu's characteristically data-driven look at the actual tradeoffs of working at startups vs. large companies — punctures a lot of myths on both sides.

“Dan doesn't moralize. He just shows the numbers and the incentives. Changed how I think about career decisions for engineers.”

apenwarr's detailed explanation of what executives actually spend their time on — mostly resolving ambiguity and making judgment calls that can't be delegated — and why that's harder than it looks.

“The best demystification of management I've read. Once you understand that the job is resolving ambiguity rather than giving orders, you understand why good executives are actually rare.”

Ben Kuhn argues that sustained attention is the bottleneck on almost everything valuable — and that our collective inability to focus is a bigger crisis than we acknowledge.

“Short, tight, and correct. I reread this whenever I notice I'm skimming more than reading.”

Charity Majors on why the 'flat org, no managers' trend is mostly a cost-cutting measure dressed up as empowerment - and what actually works.

“Charity is the only person writing honestly about engineering management. This piece is a good corrective to the 'managers are overhead' narrative.”

Ed Bradon's critical look at why complex systems fail in predictable, often absurd ways - the best field guide to contemporary systems dysfunction.

“If you've ever wondered why large organizations do obviously stupid things, this explains the mechanics. Systems have their own logic that overrides individual intelligence. Understanding this saves you from blaming people for systemic problems.”

tef argues that the goal of good code isn't extensibility — it's deletability. Every layer of abstraction you add is code someone will one day have to understand, maintain, or throw away.

“This reframing hit me hard. We optimize for the wrong thing constantly — writing code that's easy to add to instead of easy to get rid of. The section on 'copy-paste is not evil' is particularly good.”

Latent Space's deep analysis of the agent landscape - what's real, what's hype, and what architectural patterns are actually working in production.

“Cuts through the agent hype with actual technical analysis. The section on why most agent demos fail in production is worth the read alone.”

YC on what PMF actually looks and feels like

“Most founders think they have PMF when they do not - this gives you the real signals to look for”

Why you should understand something before changing it

“The single most useful mental model for anyone making decisions about systems they did not build”

Joel Spolsky's argument against rewriting software from scratch — still the most persuasive case ever made for maintaining and improving existing systems over big rewrites.

“Every team I've worked on has, at some point, had the rewrite conversation. This essay is the fastest way to explain why that's almost always the wrong call.”

What DAC is, how it works, and why it matters

“Clear explainer on the most controversial climate technology”

Vercel deep dive on tree-shaking barrel files

“If you use Next.js, this explains why barrel imports were killing your build times”