Tell me about it! - Improve your feedback game to become a better engineer
summary
Defines feedback as four parts and gives a practical feedback formula: identify the observable action, decide corrective vs evaluative judgment, name the original controlling source and its trust level, and choose a transmission channel. Shows concrete feedback channels—code reviews, CI errors, retrospectives, RFCs—and flags common failures like non-feedback as feedback (gossip, judgment, advice). Recommends diverse reviewers, using the Yari window to find blind spots, and tuning bodily reactions as a built‑in feedback signal.
AI-written summary · about
chapters (6)
- 0:00Introduction to feedback
- 2:13What is feedback?
- 8:58Working with feedback daily
- 17:33Common feedback gaps
- 24:31Feedback for personal growth
- 37:56Closing thoughts
related talks
20mFeedback Doesn’t Have to be a Fuc*up
53mTell me about myself: Feedback as a tool for development
01h 01mThe Power of Performance Feedback
42mHow to Lead Open Source Projects and Teams with Better Feedback
05mFeedback Week
46mBetter: Fearless Feedback for Software Teams
14mPeer Feedback Processes in the Game Industry
30mIntroducing a Peer Feedback Concept in Development Teams