Meta · 18 min read
First Principles
Reason from irreducible truths instead of analogies, slogans, or inherited procedures, especially when learning technical systems like networks.
Why this exists
Most explanations stop at 'how we usually do it.' That is fine for routine work and fatal when the usual way fails, changes, or was never justified.
First-principles thinking exists so you can rebuild understanding from necessities: constraints, mechanisms, and definitions that survive fashion.
On a path through the internet, this habit is the difference between memorizing acronyms and being able to debug a black hole at 2am.
Axioms & primitives
- 01A claim is only as strong as the assumptions it rests on.
- 02Complex systems are compositions of simpler mechanisms.
- 03If you cannot restate a concept in simpler parts, you do not yet own it.
- 04Analogies are scaffolding; mechanisms are the building.
- 05Foundations are revisable under better evidence; they are not dogma.
Learning objectives
After this lesson you should be able to:
- Separate a slogan from a mechanism in a networking explanation.
- List hidden assumptions in a claim and label each as observed, inferred, or borrowed.
- Derive a short explanation of packets or DNS from constraints upward.
- Identify when analogy helps and when it starts lying.
Progressive depth
Read the layers in order for a full explanation. Or open the layer you need.
Intuition
Imagine explaining a bicycle to someone who has never seen one. You could say 'it is like a scooter with pedals' (analogy). Or you could start from balance, wheels, leverage, and force transfer (first principles). The second path is slower at first and stronger later, because it survives when the analogy breaks.
Networking is full of scooter analogies: 'TCP is a phone call,' 'DNS is a phone book.' Useful, until you need to know what happens when the phone book lies or the call's packets take different roads.
First principles is the habit of asking what problem exists, what constraints bind solutions, and what mechanism actually enforces the outcome.
Formal shape
A first principle is a proposition you treat as foundational for a given inquiry: not because it is eternally true, but because further reduction is not useful for the problem at hand.
Reasoning from first principles means deriving conclusions from those foundations via explicit causal or logical links, rather than pattern-matching to nearby examples.
Method: (1) state the question, (2) list candidate foundations, (3) discard decorative claims, (4) derive the mechanism, (5) test against a counterexample.
In this curriculum, axioms at the top of each lesson are candidate foundations. Challenge them; do not worship them.
Worked examples
Networking: instead of memorizing 'HTTP is a request-response protocol,' ask what problem exists (remote machines need a shared conversation shape), what constraints apply (unreliable links, many clients), and what minimal rules solve it.
Encryption: instead of 'HTTPS is secure,' start from eavesdropping on shared media and the need for confidentiality and authenticity without a private courier.
False friend: 'The cloud is just someone else's computer' is a partial first-principles cut. It helps, then fails to explain durability APIs, multi-tenant isolation, and failure domains. Push one layer deeper when the slogan stops paying rent.
Edge cases
Not every task warrants full rebuild: cooking dinner rarely needs particle physics. First principles shines when transferring knowledge, debugging confusion, or inventing.
Foundations can be wrong; treat axioms as revisable under better evidence.
Teams sometimes weaponize 'first principles' to dismiss expertise. Real practice balances rebuilds with respect for hard-won operational knowledge.
Time box the rebuild. Infinite regress is a failure mode of the method.
Mental models
Strip and rebuild
Remove jargon and steps until only necessities remain, then reassemble upward.
Assumption ledger
Write every hidden assumption. Mark each as observed, inferred, or borrowed.
Load-bearing vs decorative
Ask which sentences, if removed, make the system stop working. Keep those; treat the rest as optional color.
Common misconceptions
Myth
First principles means ignoring all prior knowledge.
Reality
It means auditing prior knowledge: keep what is grounded, discard what is cargo-culted.
Myth
Only geniuses reason from first principles.
Reality
It is a habit of asking 'what must be true?' and rebuilding: trainable, not mystical.
Myth
If experts use jargon, jargon must be foundational.
Reality
Jargon can compress real mechanisms or hide missing ones. Demand the mechanism.
Myth
First principles means starting from particle physics every time.
Reality
Choose the right altitude of irreducible for the problem. Dinner does not need quarks.
Exercises
Work these without looking up answers first. Check yourself against the intent notes.
Exercise 01
Take the slogan 'the network is unreliable' and rebuild it into three concrete mechanisms that can fail.
What good looks like
Loss, reorder, delay/corruption/partition; ties to packets/links/routers rather than vibe.
Exercise 02
Write an assumption ledger for 'we can just block all ICMP to be safer.' Mark each assumption.
What good looks like
Surfaces PMTUD, diagnostics, IPv6 ND reliance; labels security vs breakage assumptions.
Exercise 03
Explain packets to a smart beginner without using the words packet, TCP, or IP at first; then map your words onto the real terms.
What good looks like
Forces constraint-first explanation; then reintroduces standard names.
Uncertainty notes
- Original meta-toolkit pedagogy; no catalogue URL attach required.