Ouch. That's a really bad pun. Sorry. My hope is that you will completely forget about it after reading this story from Rick Harris (yes, the same Rick Harris who brought us ISwissArmyKnife and other weird interface implementations).

Enjoy ...

I once worked on the B2B site for a manufacturer. One of their plants had a practice for years that assigned each of their clients a certain day of the week to call and place their order for their next production run. I guess it was to make it easier for planning each day's run. I don't know. But if you called on the wrong day they would tell you to call back and place your order on your assigned day.

When they moved the ordering system onto the web, they insisted on preserving this practice. So if you were the client and logged onto the web site to place your order on other than your assigned day it would display a message to you and then boot you off the site.

Better still, if you didn't have an order for that week, they made the client log in (on their assigned day, of course) and click a button that says "No order this week". And the clients all did this!


And as an unrelated footnote, thanks to everyone who pointed me to CAPTCHA resources. I ended up implementing the MSDN sample code that Joe linked me to, and have been forum-spam free ever since.

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!