Talk to me! The art of reporting a bug (and handling the feedback)
summary
Concrete rules and concrete failures: provide a repeatable sample and exact steps, try the compiler and debugger as standalone tools, attach logs and list compiler and debugger versions plus OS and toolchain details. Say when a patch download is corrupt and insist on a full binary reinstall, note surprises like Vim plugin conflicts, MinGW version vs GCC confusion, CMake pthread linking differences, and WSL/permission-mounted filesystem mismatches so engineers can reproduce and fix the real problem.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:18The problem
- 0:53The ideal algorithm
- 1:49Support as a learning channel
- 2:15Handling feedback
- 4:12Feedback instruction
- 5:19Patch update
- 6:09Crazy cases
- 7:21User feedback
related talks
40mThe art of asking questions
01h 09mPlenary: Coping With Other People's C++ Code
47mWhen to give up, and how?
26mCommunication: What are you Thinking About?
49mDebugging with the Scientific Method
10mHow to Win an Argument with a Maintainer
41mCracking the Code Review from Guesswork to Automated Guidance
52mKeynote: Steps to Wisdom