Which Skill do you want to build?
Engineering / Technical
Respect Reality
The discipline of trusting what actually happens over what a plan or a principle says should happen.
Engineering / Technical
Systems Thinking
The ability to understand how interconnected components, relationships, feedback loops, and constraints work together to shape outcomes over time.
Engineering / Technical
Simplify the Problem
The ability to see when a problem is more complicated than it needs to be, and to find the simplest structure that still explains it correctly.
Engineering / Technical
See the Pattern
The ability to notice that different problems are often the same underlying structure showing up in different situations.
Engineering / Technical
Build Around Core Principles
The ability to compress many decisions into a few core principles, so a system stays coherent as it grows.
Engineering / Technical
Decide From the Details That Matter
The judgment to tell which details actually change a decision, and which ones are just noise dressed up as information.
Engineering / Technical
Stock-Flow Thinking
Separating what has accumulated from what is currently changing it.
Engineering / Technical
Delay-Response Mismatch
Matching the pace of your decisions to how long a system actually takes to respond.
Engineering / Technical
Hierarchy and Suboptimization
Seeing when a part performing well is quietly making the whole perform worse.
Engineering / Technical
Information Flow Mapping
Tracing where information actually travels — not where it should — before blaming a decision.
Engineering / Technical
Paradigm Transcendence
Treating the framework you're using to judge a problem as something you can examine, not just apply.
Intellectual / Learning
Structural Learning and Transfer
Learning the structure behind information instead of memorizing the information itself.
Intellectual / Learning
Intelligent Problem Decomposition
Breaking a vague, tangled problem into parts small enough to actually reason about.
Engineering / Technical
Reasoning From First Principles
Rebuilding an answer from what's actually true, instead of copying what's already been done.
Engineering / Technical
Designing for Scale
Designing something to still work well at 10x and 100x the volume, not just at the size it is today.
Engineering / Technical
Optimizing the Whole System
Judging every improvement by whether the whole system got better, not by whether the one piece you touched did.
Engineering / Technical
Closing the Feedback Loop
Getting real-world results back into your thinking as fast as possible, so the next attempt is sharper than the last.
Engineering / Technical
Designing for the Real World
Designing something to survive being built, repeated, and maintained by ordinary process — not just to work once for its maker.
Engineering / Technical
Judging Technology by the System It Sits In
Reading a piece of technology through the whole system around it, since a result depends on the bottleneck, not the best single part.
Engineering / Technical
Spotting a Real Inflection Point Before It's Obvious
Watching the trajectory of a capability instead of its current state, so you notice a genuine shift before it becomes common knowledge.
Engineering / Technical
Evaluating Technology by Ecosystem Value, Not Just the Product
Judging a platform by the ecosystem it enables others to build on, not by treating it as just a bigger product.
Engineering / Technical
Designing Across Layers Instead of Optimizing One Piece
Seeing that many technology problems live at the seams between layers, so the biggest gains come from changing relationships, not adding features.
Engineering / Technical
Finding the Real Bottleneck Before Investing in a Fix
Treating a system as defined by its most limiting part, and measuring performance by whether it actually changes the economics.