Handling Uncertainty
summary
Seniority increases uncertainty: low‑level work asks how do I implement this, senior roles ask are we building the right thing and must weigh strategy and hiring. Practical moves include asking clarifying questions (one question saved six months of work), running short spikes to test feasibility, using tests, code review and pairing to reduce surprises, and practicing chaos engineering — expect it to break the system the first time. When information stops improving, quantify risks and place a deliberate bet.
AI-written summary · about
chapters (16)
- 0:00Introduction to uncertainty
- 1:04Uncertainty in software development
- 3:17Types of uncertainty
- 5:46Career ladder and uncertainty
- 7:13Uncertainty grows with seniority
- 10:05Uncertainty risk and complexity
- 11:55Decision paralysis and inaction
- 13:20Recognizing decision paralysis
- 14:22Increasing certainty with information
- 16:35Assessing risks when certainty is maxed
- 18:24Making choices and handling failure
- 19:47Career choices and trade-offs
- 20:31Reducing uncertainty in software
- 23:23Handling uncertainty actively
- 24:29Practical tips for uncertainty
- 26:16Conclusion and final thoughts
related talks
51mNavigating Uncertainty in Software Development: Effective Planning Techniques
29mAm I ready to be a Senior Engineer?
33mBuilding Sustainable Teams to Handle Uncertainty
25mHow to Drive Cross Team Techincal Changes
43mBetter Software Development Systems through Stress
22mHow to be an inefficient developer?
47mAgile experience in changing environments and the challenges faced
24mFrom Startup to Scale Up Designing for Growth from Day One