A junior dev submitted their first PR. One variable is named wrong. → "This is wrong.", Someone proposed using a new library in standup. → "No.", A teammate pushed code that broke the staging build. → "Did you even test this?", A function returns null instead of an empty array. → "This doesn't work.", A designer delivered a mockup without mobile screens. → "Not what I asked for.", A teammate refactored a module and introduced three bugs. → "Start over.", A developer used an unconventional but working solution. → "I'm sure this made sense when you wrote it.", Someone presented a new feature architecture in a meeting. → "Interesting approach.", A teammate submitted a PR two hours before the deadline. → "As always, the deadline was more important than quality.", A colleague's bug fix introduced a new issue. → "I'll fix it myself, it's faster.", A developer wrote deeply nested conditional logic. → "Good luck maintaining this in six months.", A junior wrote their first API endpoint — it mostly works. → "Thanks for… trying.", A developer forgot to handle a null case. → "This is a basic mistake. Please review the fundamentals.", The same naming convention issue appeared in a second PR. → "We've discussed this pattern before. I shouldn't have to repeat myself.", A backend dev wrote their first frontend component and got the state management wrong. → "Anyone with experience in this area would know not to do this.", A function has O(n²) complexity where O(n) is possible. → "I don't have time to explain why this is bad — just Google it.", A mid-level dev submitted a feature that works but isn't optimized. → "This is junior-level work.", A teammate sent a technical spec document for review. → "Everything here is a problem.", A developer implemented a caching layer. → "The logic is completely wrong.", A PR touches 14 files and mixes refactoring with new features. → "This is a mess.", A junior submitted a data migration script. → "None of this is acceptable.", A teammate proposed a microservices split for a monolith. → "The whole approach is off.", A developer accidentally pushed console.log statements to production. → "Wow. Just… wow.", A hotfix for a bug introduced two new ones. → "Congratulations, you've made it worse.", A teammate chose to store session data in localStorage. → "Bold choice.", A PR has no tests and the deadline is tomorrow. → "Sure, let's ship this and see what happens.", A developer keeps submitting PRs without addressing previous review comments. → "I've reviewed this three times now and every time there are new issues. I don't know what's going on but this needs to stop.", A teammate reopened a PR that was closed for rework, without making changes. → "This PR sat in review for a week and it still has the same problems I flagged last time. Is anyone actually reading my comments?".

Improve feedback

by
Print
Embed

Leaderboard

Visual style

Options

Switch template

)
Continue editing: ?