What to Expect When You're NOT Expecting - Go Time Podcast Day 1
summary
Practical debugging beats theory: quick printf/pretty-print with %+v often outpaces heavy tooling for fast feedback, but when stepping or changing state is needed use Delve (it relies on DWARF and can be driven via a JSON-RPC server) or IDEs that call it. Linux eBPF + uprobe tracing captures every Go function call without stopping the process and can even inject or modify memory (use cautiously); Weaver prototypes per-call tracing for live inspection.
AI-written summary · about
chapters (8)
- 0:00Introductions and definition
- 2:26Debugging techniques
- 8:11Understanding delve
- 13:25Debugger internals and IDEs
- 21:24Tracing and eBPF
- 34:33Development and tooling
- 39:09Delve roadmap and future
- 45:00Unpopular opinions and wrap
related talks
20mDebugging: Techniques for Uncertain Times
01h 09mPlenary: Coping With Other People's C++ Code
17mIf You’re Happy and You Know It (Inside the Mind of a Developer)
49mDebugging with the Scientific Method
40mWorst. Ideas. Ever.
47mWhen to give up, and how?
48mHow to Talk to Developers
54mTech Truth: Agile Evolution & the Future of SW Engineering