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
- Do the simplest thing that could possibly workseangoedecke.com
- Everything I know about good system designseangoedecke.com
- What is First Principles Thinking?fs.blog
- Invisible Details of Interaction Designrauno.me
- Computers can be understood - Made of Bugsblog.nelhage.com
- Up and Down the Ladder of Abstractionworrydream.com
- Rambles around computer sciencehumprog.org
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Thinking like Transformersrush.github.io
- behind the scenes of paper writingsophielwang.com
- To Understand Language is to Understand Generalization | Eric Jangevjang.com
- Human Judgment as a Specificationblog.brownplt.org