Nuance is very important. When one speaks, sometimes they ignore the nuance of the other side. Therefore, they never get to truly know the other side, and true harmony can never be achieved. Sometimes, those who claim or imply to be nuanced, are the very ones who are the least nuanced. If one side is pushed into a corner, they will fight back, hard.

I am glad that this issue is being addressed. I think it is also worth mentioning, that it is more worth the time to document your code now, than it is to waste time later, trying to figure out what the code does. Many project leads are unwise when it comes to this, and therefore fail to allocate the proper time. This will inevitably lead to unmaintained/unreadable code later down the road. This is bad for many reasons: You cannot reuse the code, you cannot maintain old code, programmers will become angry, ETC…