Thinking Like an Engineer
What does it mean to think like an engineer, and what can anyone borrow from it?
A route from the ideal of the philosopher-engineer through diagnosis, estimation and physical models to systems and design for failure, ending in an ordinary kitchen. Each step swaps a feeling for a check: what does this observation establish, what did I assume, how does this behave near its limit, and what happens when a part fails or lies.
-
The Philosopher-Engineer: Study and Workshop Together Liberal Arts & Reasoning
Begin with the ideal: the philosopher asks what is true and good, the engineer asks what works, under what constraints and how it fails, and five habits drawn from Leonardo, Archimedes, Franklin, Leibniz and Peirce show the two halves correcting each other.
-
Evidence-Based Troubleshooting: Separating Explanations Engineering & Career
The engineer's first discipline is diagnosis, in four drills (the ping works but the site does not, the tunnel is up but the application is down, everything is green, an event came before a failure) that ask what each observation actually establishes and which next test would change what you do.
-
Quantitative Reasoning with Stated Assumptions Engineering & Career
Estimation comes next, with examples small enough to check by hand (a byte counter turned into 0.6 percent utilisation, a restore that takes about 83 or 89 minutes depending on whether the size was in GB or GiB) showing that the arithmetic is easy and the assumptions are where mistakes live.
-
String physics The Science of Sound · interactive
Try the habit on a physical model: Mersenne's law makes frequency rise with the square root of tension, so a two-semitone bend needs about 26 percent more tension, and the page openly corrects its own earlier version, which had the relation backwards.
-
Systems Thinking: Feedback, Queues, Information and Dynamics Mathematics, Systems & Languages
Scale up from one string to systems, where stocks, flows and delays explain overshoot and a simple queue shows nonlinearity again: at 90 percent utilisation each job spends about ten times its service time in the system, and at 99 percent about a hundred times.
-
Systems, Decisions and Robust Design Liberal Arts & Reasoning
Once structure explains behaviour you can design for being wrong: ask of every component what happens when it fails or lies, prefer redundancy with independent failure modes, staged rollout and rollback plans made in advance, and ask what keeps a system open to correction.
-
The Practical Kitchen: Staples, Meal Prep and Food Safety Health & Nutrition
Finish by taking the habits home: set up the kitchen so that eating well needs less willpower, compare cost per usable serving with your waste assumption written down, trust a food thermometer over a fixed microwave time, and check where a rule comes from, as the page does for dry kidney beans: the FDA's 30-minute boil builds a safety margin over the 10 minutes one laboratory study found enough to destroy the toxin.