Take a step back
summary
Real examples and clear fixes decide whether this is worth watching: concrete claim that two simple habits—structured writing and check yourself frequency—reduce autopilot and tunnel vision; a tool recommendation of rubber duck debugging as a written-thinking substitute; a project case where a new framework launches with zero adoption because no one steps back; and a testing story where parallelizing end‑to‑end runs shortens CI now but incentivizes costly test bloat later.
AI-written summary · about
chapters (11)
- 0:00Coding versus human understanding
- 2:27Autopilot and tunnel vision
- 8:52Autopilot risks in engineering
- 9:34Autopilot mistakes examples
- 10:17Taking a step back effectively
- 15:52Critical thinking strategies
- 16:56Organizational tunnel vision
- 18:11Questioning technique
- 21:05Importance of strategy
- 23:16Tactical fixes consequences
- 24:41Why stepping back matters
related talks
57mDebug your thinking
21mWhat else can we automate? How to extend your skills and keep learning
20mFailing Can Be Good! Bringing a Growth Mindset to Every Project
50mEmbracing Simplicity
41mWant to make a change? Stop talking and start listening
44mBehavioral Software Engineering
55m14 Identifying And Removing Impediments
25mWork On The Wrong Things First