Collaboration & Feedback ยท Lesson 3 of 3
Taking code-review feedback
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Code review is about the code, not you. Judge each comment on whether it's right, talk through what you disagree with, and make the changes you accept.
In your work
A reviewer says your fix to a client's export runs a database query for every row, and suggests one query instead. You check, agree and change it, then reply to another comment you disagree with, adding a benchmark.
What the UK rules say
- The BCS Code of Conduct asks IT professionals to seek, accept and offer honest criticism of their work.
What to do
- Read each comment as a point about the code, not a verdict on you.
- Ask questions when a comment isn't clear.
- Agree and change it, or disagree with reasons.
Watch out for
- Defending every line by reflex.
- Resolving comments without replying.
In your organisation
What are your team's code review guidelines, and how quickly should reviews be answered?
Your employer's own policies come first.
Sources
- BCS, BCS Code of Conduct (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
