Working Smarter: 5 Steps To Getting Unstuck
summary
Five concrete steps for getting unstuck: reproduce and read the error, Google a specific query, inspect related files, ask a teammate with open-ended context, then step away. Example uses Rails, Vue.js, RSpec and Capybara to write a system test for user signup; the surprising fix is adding Devise :validatable in the user model so password presence is enforced. The test then passes, showing the 5 steps produce a working, time-saving result.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:48Five steps to getting unstuck
- 5:21Step one: Troubleshoot errors
- 6:47Step two: Google specific queries
- 8:57Step three: Examine code closely
- 10:42Step four: Ask coworkers for help
- 12:48Step five: Take a break
- 15:37Summary of the five steps
related talks
38mGetting Unstuck: Strategies For Solving Difficult Problems
31mGetting Unstuck
52mKeynote: Steps to Wisdom
11mGetting Beyond Bewilderment
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
49mDebugging with the Scientific Method
20mDebugging: Techniques for Uncertain Times
01h 18mKeynote: Steps to Wisdom for C++ Developers