News for hackers. Stuff that matters.
Re:Joel on Software: Anecdotes by jerf on Wednesday November 19, 2008 @01:38PM (#369757)
I'm coming around to the point of view that when somebody complains about simplification or incompleteness, that they should simply be ignored. As long as the simplification isn't actively wrong and the incompleteness isn't deceptive by leaving out contrary evidence, one must be aware that all forms of work are limited.

Jeff Atwood took a lot of flack in his recent NP post simply because he dared describe the problem in non-mathematical terms. He may also have been wrong, but I am inclined to think his explanation was (correctly) too simplified to really be wrong... but still, right now I'm talking about the people who flamed him for failing to include a complete computer science textbook in his blog post.

Yes, I am so sorry that in my blog post ruminating on how unit testing seems to affect my Python coding that I did not include a complete, correct Grand Unified Theory of the universe complete with how to apply it at the macroscopic level and use it to predict who will win the Presidential election in 2016 and create a superhuman-intelligent AI. At some point you to understand that any given work has boundaries.

I've become sensitive to this because I actually have fallen for the trap of trying to be too inclusive, and it's worthless. Stop complaining about it. Or, at the very least, when complaining that work X should have included Y, you should say what should have been cut instead and why it would be an actual improvement in the end product, preferably beyond "I would like it better".

There are no comments on this comment yet.