Why good programming is also bad communicating 3

[Sympology]

What you guys are describing not only applies to programming, but to all design work.

To often I find massive holes in work.

I usually start of by saying something like.

If I put x in y box, it comes up with an unexpected error.

Very bad designer.
Tell them not to do that. It's not made to take X.

Bad designer:
Ahh, Ok I'll make so they can't put X in box Y

Good designer:
Ahh, Ok I'll make so they can't put X in box Y, but is there a reason why they are doing that in the first place?



Robert Wilensky:
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true.

 

[philhege]

Comments, yeah.

There's one in earlier versions of the Crystal Reports ActiveX reader. Somebody annotated a <DIV> with

<!-- This extra div gets rid of unwanted white space in Internet Explorer.  I don't know why though. -->

Phil H.
Some Bank
-----------
Time's fun when you're having flies.

 

[Trevoke]

If we switch to comments and such, my favorite Tip of the Day was from Microsoft Visual C++ (6, I think).

"Always comment your code as though the person who will maintain it is a maniacal serial killer who knows where you live."

Tao Te Ching Discussions : Chapter 9 (includes links to previous chapters)
What is the nature of conflict?