4 ms·
No, they would need to communicate about the ideas and thought processes behind every individual line of code. If not now, then the next time there's a bug in s
by tremon 5y ago
No, they would need to communicate about the ideas and thought processes behind every individual line of code. If not now, then the next time there's a bug in said lines.
- falcolas 5y ago> ideas and thought processes behind every individual line of code I realize you're being hyperbolic (at least as hyperbolic as the parent), but this is one of the big hangups of pair programming for me: waiting for folks to get through boilerplate. Let's talk ideas and thought processes about the important (or at a minimum non-boilerplate bits of) code, not an entire programming session. "Alex, what were your thought processes that lead you to use 'i' for a loop variable?"
- tremon 5y ago"Alex, what were your thought processes that lead you to a for loop here, rather than a {while loop/list comprehension/map operation/linq expression}?"