While I agree with much of the article, one note I find important from my pair programming exercises is that pointing out typos is nit-picking and slows the who

While I agree with much of the article, one note I find important from my pair programming exercises is that pointing out typos is nit-picking and slows the whole process down. It interrupts the flow of the programmer and doesn't contribute anything useful, since the compiler will point out all typos in due time. (All things in moderation: if it's the sort of typo the compiler won't catch and will cause unexpected behavior, then point it out by all means). This sort of mentality is important to consider on higher levels as well. We need to find what actually improves the development process and focus on doing those things while at the same time refraining from doing things that slow down the process.