D
5

That time my code review at a meetup backfired on me

I was at a local coding meetup in Denver last month and got asked to review a beginner's project on stage. I jumped in and pointed out 5 mistakes right away, thinking I was helping. But the guy looked crushed and I realized I came off like a jerk. Has anyone else learned the hard way that timing and tone matter more than being right?
3 comments

Log in to join the discussion

Log In
3 Comments
rowan_butler93
Public critique should be private first. Basic rule.
6
smith.jordan
smith.jordan18d agoMost Upvoted
Wish I learned that before my email accidentally went to the whole company.
3
the_mary
the_mary15d ago
People forget that once you hit send on a public critique, you can't take it back. A quick private message first gives the person a chance to adjust or explain before everyone else jumps in. In my experience, most issues get resolved way faster when you handle it one-on-one instead of putting someone on blast. Your mileage may vary, but taking that extra five minutes has saved me from a lot of awkward conversations.
-1