lessons

First principles

Practical lesson page — first-principles reasoning as used in Musk-linked engineering culture, with examples and limits.

Topics: lessons

Tags: first-principles engineering playbooks

First principles is the highest-frequency “Musk method” lesson. Muskularity treats it as a useful engineering habit, not a magic spell and not a personality cult.

Definition (working)

Break a problem into fundamental truths you can justify, then rebuild the solution upward — instead of only copying analogies (“that’s how the industry does it”).

Where it shows up (examples, labeled)

DomainExample patternLabel
RocketsQuestion material cost vs finished part cost; reusability economicsCommon public explanation in talks; verify quotes via primary video
Cars / manufacturingChallenge supplier norms; redesign for production rateInterview/event claims — source per story
TunnelsCost-per-mile skepticism toward legacy tunnelingCompany narrative + project evidence separately
AICompute/energy as first-class constraints, not afterthoughtsSee AI Wars / Colossus

How to use it (playbook)

  1. Write the goal in one sentence.
  2. List assumptions you inherited from industry analogy.
  3. Mark each assumption: verified / assumed / unknown.
  4. Rebuild only from verified + testable unknowns.
  5. Run a cheap experiment before a worldview.

Limits (do not skip)

  • First principles without data becomes confident speculation.
  • Physics constraints are not business model constraints — keep them separate.
  • Organizations still need process, safety, and regulation; “question everything” is not “ignore laws.”
  • Media soundbites compress years of iteration into a slogan.
  • Speed and iteration
  • Manufacturing
  • Talent density
  • Capital allocation
  • Narrative and attention

Source posture

Prefer primary interviews and technical talks for quotes. Prefer company/engineering write-ups for implementation claims. Prefer third-party reporting when evaluating whether the method produced the claimed outcome.