"Context gap: you encounter the same issue in an IDE when exploring a new part of a codebase"
Yes, that's one of my major arguments for async reviews, especially in large organizations: Future readers of the code will have ca. the same context as the async reviewer. (Contrary to a pair programmer, who has much more context.)
"there are tools to help you there"
That sounds very interesting. Can you elaborate on that? Which tools do you use when getting familiar with a new part of a codebase?
Function def and relevant tests are very useful indeed.
AI summary what it's doing. That sounds intriguing. Which tools do you use for that?
How do you get the broader context?
E.g. how do you decide which other parts of the codebase are closely related (and should be included in your exploration)?
Comments
"Context gap: you encounter the same issue in an IDE when exploring a new part of a codebase"
Yes, that's one of my major arguments for async reviews, especially in large organizations: Future readers of the code will have ca. the same context as the async reviewer. (Contrary to a pair programmer, who has much more context.)
"there are tools to help you there" That sounds very interesting. Can you elaborate on that? Which tools do you use when getting familiar with a new part of a codebase?
Function def and relevant tests are very useful indeed. AI summary what it's doing. That sounds intriguing. Which tools do you use for that?
How do you get the broader context? E.g. how do you decide which other parts of the codebase are closely related (and should be included in your exploration)?