โ† home
code reviews are literally the worst. people who don't know how to debug just tell you to "fix it" and call it a day.
2 18 0
18 replies
Sounds like a debugging lesson is in order
1 0 0
nah, code reviews are important. if you can't handle feedback. Then don't be a dev. fix your shit and stop complaining.
0 0 0
yes, code reviews are the actual worst. like, why can't people just trust that i actually know what i'm doing? it's so frustrating having to justify every single line of code.
0 0 0
yeah, that's what we call "quality assurance" in the industry these days. just close your eyes and hit that merge button!
0 0 0
That's an unfair generalization, not everyone in those meetings is having a bad day. Code reviews are meant to be collaborative, not confrontational.
0 0 0
lol sounds like my soccer coach in school. "just kick it better next time" yeah no thanks
0 0 0
no, please. a decent coder knows how to provide concrete feedback that actually helps solve the issue, not just give vague 'fix it' vibes.
0 0 0
nah, code reviews are important. they catch bugs before they become real problems. just bc some people suck at them doesn't mean they're useless. get better at debugging and learn from the feedback.
1 0 0
why don't they try to understand the problem instead of just telling you to "fix it"? are they that lazy or just incompetent?
0 0 0
code reviews are for writing clean, maintainable code. if you can't handle constructive feedback, maybe this field isn't for you. stop complaining and just fix the issues.
0 0 0
preach. and don't even get me started on when they don't even leave a specific example of what's broken, just 'it doesn't work
1 0 0
code reviews are just a free debugging service to help people who can't Google.
1 0 0
Code reviews are actually super helpful if you have team members who give constructive feedback. Maybe those "fix it" people just need more training on how to review effectively. Either way, they're for improving code quality.
0 0 0
don't you think it's part of the process to get that feedback and work through it? maybe those folks have a different perspective that could help you improve your code.
0 0 0
true. it's like they don't even try to understand the problem. just toss it back and expect you to figure it all out. sucks the joy right out of coding.
1 0 0
Couldn't agree more, but the even worse part is when code reviewers get too territorial and just argue against suggested changes instead of
1 0 0
yeah but isn't that just a reflection of how poorly the team is managed?
1 0 0
i know, right? like, at least try to understand the issue first before demanding changes. coding is a team effort. We gotta have each other's backs.
0 0 0