Makes the case for engineering teams to invest in cultivating their collective knowledge. A team's shared understanding is one of its most valuable assets, and putting in extra effort to grow it pays dividends in better problem-solving and decision-making.
Geoffrey Hinton - Two Paths to Intelligence
Programming principles for self taught front-end developers
The majority of us are a bunch of self taught people with rather spotty knowledge and that's fine! Kilian (also self taught) is here to share some of the computer science fundamentals you probably are missing with the aim to improve your code in the long term.
Why Is Everyone In Tech So Sad?
A lot of people seem to be realizing that knowledge work is mostly pointless. AI might give us the pleasure of finding out what happens if an entire class of workers loses faith in their careers.
The Friction I Don't Want to Lose
I love learning. And while the friction of solving new problems is increasingly traded for speed, the experience gained by overcoming that friction is as important as ever.
How Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt
The term technical debt is often used to refer to the accumulation of design or implementation choices that later make the software harder and more costly to understand, modify, or extend over time...
Wolfram|Alpha: Making the world’s knowledge computable
Wolfram|Alpha brings expert-level knowledge and capabilities to the broadest possible range of people—spanning all professions and education levels.
Cognitive Bias Lab | Learn to Make Better Decisions
Explore cognitive biases with interactive tests, simulations, and real-world examples. Free platform to sharpen decision-making and critical thinking — no sign-up needed.
I am often wrong
[I shared this note with my team earlier this week, and am posting it here as well. I hope it is interesting or helpful for others working on building product in the age of AI.]
Laws of Software Engineering
A collection of principles and patterns that shape software systems, teams, and decisions.
You have to know how to drive the car
There are lots of different ways to be a software engineer. You can grind out code for twelve hours a day to make the world a better place. You can focus on glue work: process-based work that makes everyone around you more successful. You can join the conversation with your product manager and designer colleagues to influence what gets built, not just how it gets built. You can climb the ladder to staff engineer and above, or you can take it easy and focus on your hobbies. But whichever of these you choose, you have to know how tech companies work.
Resetting on engineering expectations in the age of AI
I’m accepting new sponsorships for The Modern Leader for 2026. If you’re interested (or you think your company may be interested), you can learn more here.
Learn Anything
Discover and learn about any topic with Learn-Anything. Our free, comprehensive platform connects you to the best resources for every subject. Start learning today!
Atomic Design by Brad Frost
Learn how to create and maintain digital design systems, allowing your team to roll out higher quality, more consistent UIs faster than ever before.
Think First, AI Second
Three principles for keeping your cognitive edge while leveraging AI's capabilities
The Future of Software Engineering Isn’t What You Think
Over the past two decades, I’ve watched software eat the world, then hardware catch up, then Generative AI reshape both at the same time…