11 December 2004

Dilbert enters the RSS Zone

Quick tip Here's the RSS feed for Dilbert and the workaround to get it tailored to a limited number of entries.

Dilbert enters the RSS Zone

If you are one of three monkeys in the forest and cover your ears, you cannot hear the feeds with bad information. Too succeed, all you have to do is differentiate and provide simple instructions.

The key to understand RSS is that anyone who dares appear at the conference with a novel idea is celebrated. All those conferences. Now the fun starts.

Too bad the solution is irrelevant. Some chomp ice. Others like to blog. Yet, with so many blogs, where's the real dialog with the customer?

Rather than use blogs to communicate new ideas, they spend their time talking about everything but what needs to be done to get RSS to actually work as advertised.

The true sign of a problem is when the RSS community talks about e-mail, but then has to explain "Why are you using e-mail when you could be using feeds." The RSS community doesn't know what to do when the customers turn out to be auditors. The old games no longer work.

The goal of XML is to confuse even the developers. The solution is to have meetings. Not to solve problems, but to give your developers a chance to vent. They have succeeded.

RSS community has long known about the problems. But they have no progress. Just more meetings. They wonder why the funding is limited.

Notice what the RSS community eats. They like to recycle. Interesting to find out the coders are unable to use the software they deride.

So much talent. If your code doesn't work right, just blame the customer. RSS: You can't stop after you've started -- RSS feeds, you can't stop with just one nibble.

If you want to know about RSS, study. The big sign of a problem is when the coder actually believes they can get away with it. They are wrong.
Quick tip Here's the RSS feed for Dilbert and the workaround to get it tailored to a limited number of entries.

Dilbert enters the RSS Zone

If you are one of three monkeys in the forest and cover your ears, you cannot hear the feeds with bad information. Too succeed, all you have to do is differentiate and provide simple instructions.

The key to understand RSS is that anyone who dares appear at the conference with a novel idea is celebrated. All those conferences. Now the fun starts.

Too bad the solution is irrelevant. Some chomp ice. Others like to blog. Yet, with so many blogs, where's the real dialog with the customer?

Rather than use blogs to communicate new ideas, they spend their time talking about everything but what needs to be done to get RSS to actually work as advertised.

The true sign of a problem is when the RSS community talks about e-mail, but then has to explain "Why are you using e-mail when you could be using feeds." The RSS community doesn't know what to do when the customers turn out to be auditors. The old games no longer work.

The goal of XML is to confuse even the developers. The solution is to have meetings. Not to solve problems, but to give your developers a chance to vent. They have succeeded.

RSS community has long known about the problems. But they have no progress. Just more meetings. They wonder why the funding is limited.

Notice what the RSS community eats. They like to recycle. Interesting to find out the coders are unable to use the software they deride.

So much talent. If your code doesn't work right, just blame the customer. RSS: You can't stop after you've started -- RSS feeds, you can't stop with just one nibble.

If you want to know about RSS, study. The big sign of a problem is when the coder actually believes they can get away with it. They are wrong.
" />