Computational Thinking
summary
Computational thinking means building executable models and iterating on them until their outputs are observable and falsifiable, not just writing code or learning syntax. Examples: a unit-mismatch causes the Mars Climate Orbiter loss of about $327.6M, medical-device software shocks a pregnant patient because tests omitted that case, teams use Jupyter notebooks for fast feedback and ADRs capture architecture decisions, and integration testing plus diverse test samples catch interface failures.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:50What computational thinking is not
- 8:15Human communication history
- 17:50Abstraction in problem-solving
- 20:21Age of computability impact
- 22:07Defining computational thinking
- 24:33Poor computational thinking consequences
- 26:42Knowledge transfer and onboarding
- 28:08Ethical obligations in software
- 30:37Q&A
related talks
50mSoftware Is Details
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
41mComputer Science, Software Engineering, and the Scientific Method
47mCode Is Cheap. Software Isn’t.
54mArchitecture & Responsible Technology
42mWhat our Brains can Teach us About Software Engineering
54mSystems Thinking
43mLearning to Live with Errors
