The bad news: It got mentioned as an example of what’s wrong with discourse in America.
Oh well. Mr. Cranky dishes it out. He can take it. And putting aside for the moment that Mr. Cranky is intended to parody criticism as much as the actual movies he’s criticizing (Mr. Cranky hates everything and rates movies on a one-bomb to four-bomb scale), I think it begs a valid question. Has discourse in America devolved to dangerous lows and is the Internet somehow to blame?
>>is the Internet somehow to blame?
Obviously you have never heard talk radio.
Sorry to add insult to injury, but you said you (or at least Mr. Cranky) can take it.
It’s not the information that is the problem it is how people internalize and utilize the information. Should we dare make someone actually think before responding to something or perhaps even trust them to take something tongue and cheek. I give the NYT three bombs on this one.
An entire Web site dedicated to battling a minor, common linguistic misusage?
I love it. I’m buying a t-shirt.
Criticising things is easy and you rarely go wrong with criticism.
On the other hand, if you recommend something you can go wrong. People who did not like what you were recommending will come back at you, like its your fault.
So recommending, or doing things in a better way, is risky and hard work compared to criticism, therefore most people rather criticise instead of recommend. It’s easier.
But written well it’s fun to read, too
Bug Bash is a comic strip written and illustrated by Hans Bjordahl. Bug Bash is a comic strip about technology: managing technology, the business of technology. It's about project management and managing projects through the dull world of Rational Rose, use cases, and requirements. Functional requirements, user requirement, functional specifications, design specifications, call it what you want but it's still the bane of project managers. And when you're done with that, you can think about all the fun that comes with timelines, scheduling, estimates (PERT estimation anyone?) and resourcing until Gantt charts are coming out of your ears. Let's not forget the risk management in the software engineering life cycle. Maintaining the project is just as much fun, managing what was initially set out in requirements and trying to keep feature creep / scope creep in check with change management. If any of these words send nightmares to you, the project manager, then this site probably rings true with you. (Who Links Here?)