Programming is Debugging
summary
Argues that coding is mostly debugging and that cost of fixes rises exponentially with bug age; gives concrete wins: enable editor syntax checks (Sublime Text 2 example), write Repro tests and use CI (CircleCI set up in five clicks, Jenkins), run linters and coverage, and prefer visual debuggers over print spam. Demonstrations include binding.pry and Chrome DevTools, a day-losing Chrome JSONP mystery, and a prototype Panorama using Ruby 2 TracePoint that records method invocations and local values.
AI-written summary · about
chapters (10)
- 0:00Start
- 7:03Read The Error
- 7:47WARNING: Errors may change during debugging
- 9:22Fast iterations maintain momentum.
- 10:34Compiler errors & warnings are your friends.
- 12:16Check the stack trace
- 15:03Get it out of your head ... via your mouth
- 16:58Create a repro test.
- 20:22Divide and Conquer
- 22:15Valid- ate your assump- tions!
