English for Developers Dictation: Code Review Conversations

Listen for the concern around the technical word. A reviewer may ask about a condition, a repeated operation or the result when information is missing. Words such as why, whether and when tell you how that concern is framed. Keep the whole clause that follows them. A function, input or test is only part of the message; the rest explains what it does or needs. You can follow these sentences without seeing the code. Preserve the spoken explanation, including any negative or suggested change.