On reasoning backwards from architecture to implicit requirements – Casey Handmer's blog
Part of my series on common misconceptions in space journalism. Rigor is the underpinning of success when designing any kind of technological application. Throughout my career I have found myself o…
Part of my series on common misconceptions in space journalism. Rigor is the underpinning of success when designing any kind of technological application. Throughout my career I have found myself on the frontiers not only of my own knowledge, but human knowledge in general. There is no handy reference or list of answers to check my work, so I was forced to develop my intuition for detecting problematic reasoning. I routinely employ these skills both to defend my own work against errors and to constructively critique the work of others. In this vein, I have previously I discussed the…
saved by
related reading
- Taste for Makerspaulgraham.com
- The Cook and the Chef: Musk's Secret Sauce — Wait But Whywaitbutwhy.com
- Akin's Laws of Spacecraft Designspacecraft.ssl.umd.edu
- Cocktail party ideasdanluu.com
- architecture astronomyindieweb.org
- Notes on the Synthesis of Formmonoskop.org
- All you need is linkssubconscious.substack.com
- Taste for Makerspaulgraham.com
- Tools for thought: science, design, art, craftsmanship? | Andy Matuschakandymatuschak.org
- Everything that turned out well in my life followed the same design processhenrikkarlsson.xyz
- Output isn’t design - Linearlinear.app
- The Rosetta Stone of Design Engineering by Yann-Edern Gillet — Yann-Edern Gilletyannglt.com