▲ | necovek 9 days ago | ||||||||||||||||||||||
It's one message I struggle to convey to people I do code reviews for: don't make me understand it, make it more self explanatory so every reader does. (And, yes, I ask for it explicitly too) (I sometimes "ask" questions for something it took me a few back and forths through code to get so they'd think about how it could be made clearer) Unfortunately, most people focus on explaining their frame of mind (insecurity?) instead of thinking how can they be the best "teacher". | |||||||||||||||||||||||
▲ | hakunin 9 days ago | parent | next [-] | ||||||||||||||||||||||
Yeah, not easy, but it helps to build some rapport first, so people learn what you’re after. The way I tend to do that is by leaving a review comment with an example code snippet that makes me understand it better, and a question “what do you think about this version? I tried to clarify a few things here.”. + Explain what was clarified. I find the effort usually pays off. | |||||||||||||||||||||||
| |||||||||||||||||||||||
▲ | kristianbrigman 8 days ago | parent | prev [-] | ||||||||||||||||||||||
One relevant side effect: AI seems to understand your code better when you do this as well. |