#Feedback
Articles about Feedback — exploring patterns, best practices, and real-world implementations in production systems.
4 posts tagged with feedback. ← All posts
The author's side of code review — turning a pull request from an ego threat into a growth loop by separating your identity from your code, responding to every comment, and pushing back with reasoning instead of feelings.
The author's side: separating your identity from your code, assuming good intent, responding to every comment, pushing back with reasoning (not ego), and turning review into a growth loop instead of an ego threat.
How to write code-review comments that improve the code and the relationship at the same time — commenting on the code not the coder, labeling severity so the author knows what blocks, asking instead of decreeing, teaching the why, and knowing when a thread belongs on a call.
Writing review comments that improve the code and the relationship: comment on the code not the coder, be specific and actionable, label severity (nit/suggestion/blocking), ask questions when you lack context, and pick your battles.
The conversations we most want to avoid are usually the ones that matter most — telling a colleague their work isn't good enough, raising a concern with your manager, addressing a conflict that's festering, giving feedback that might not be welcome. Avoiding them feels safer in the moment and is almost always worse over time: problems grow, resentment builds, and the unsaid thing poisons the working relationship. Emotional intelligence doesn't make hard conversations easy, but it makes them possible to have well — which is a learnable skill that changes everything downstream.
The conversations we most want to avoid are usually the ones that matter most — telling a colleague their work isn't good enough, addressing a festering conflict, giving unwelcome feedback. EQ doesn't make hard conversations easy, but it makes them possible to have well — a learnable skill that changes everything downstream.
Most people's experience of "performance management" is the dreaded annual review — a backward-looking, anxiety-inducing ritual that helps no one improve. That's a symptom of getting feedback wrong. Done well, feedback isn't a once-a-year verdict but an ongoing, growth-oriented conversation that helps people do their best work. The shift — from judgment to growth, from annual to continuous — is what separates performance management that develops people from performance management that just rates them. And feedback, given well, is a skill worth developing.
Most people's experience of 'performance management' is the dreaded annual review — a backward-looking, anxiety-inducing ritual that helps no one improve. That's a symptom of getting feedback wrong. Done well, feedback isn't a once-a-year verdict but an ongoing, growth-oriented conversation that helps people do their best work.
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.