Maybe we can learn from that that any assumptions made must be first verified. First quickly validate the approach you take on the task with the reviewer, prior to coding.
Note that you mentioned clearly “bug” in your initial post, i.e. bugs in production and I do think there should not be bugs if you have enough time to solve the problem (otherwise what does it mean? that someone will need to review any code you produce in the company?) ; but now you rather talk about communication issues with the reviewer, and not bugs…
So that leaves me confused ; maybe the reviewer felt the same way.
