There's an unwritten rule that lets you confess or rat on your co-workers after a year has gone by. We've gathered the best Domino bloopers of 2003 to get you thinking about what you've experienced in the workplace. Have you made any stupid mistakes? How about your co-workers or, better yet, your boss? Send us your favorite Domino or Notes blooper and your name or code name, and we'll share it for all to enjoy.
True Domino Blooper #19: Unpredictable unprocessed documents
This Domino developer got into a tight squeeze when an agent using the unprocessed document property ran amok. Read on and see what caused the disaster and how our hero saved the day.
True Domino Blooper #20: How do you tell the boss he's a moron?
This Domino maven found out first hand what happens when an unqualified exec ran riot with AdminP. This story is a perfect example of when a little knowledge combined with a lot of authority can be a dangerous combination.
True Domino Blooper #21: The error handling error
Let this Lotus developer sit you down and spin you a yarn about how he filled the hard drive on his high-end server with more than a million agent logs in less than an hour. You may get a chuckle and learn something at the same time.
True Domino Blooper #22: Tell it like it is
This Domino project leader got him self in a pickle when the mail storage monitoring project that his team was working on told users in no uncertain terms what to do with their overstuffed inboxes. As it turns out, not everyone likes barking dialog boxes, and some were howling for our hero's head.
True Domino Blooper #23: A case of the course confirmation blahs
This systems admin was more than reluctant to take on a development project handed to him by a boss who was still wet behind the ears. Find out what happens when a cross-eyed, butter fingered project manager accepts the hand off.
True Domino Blooper #24: Agent faux pas
This Lotus CLI had his class up in arms when he was explaining scheduling details for agents. Call the union? It turns out that some students in the class thought that they were the agents in question.
True Domino Blooper #25: Don't get locked out
This Domino network manager was trying to help an admin get his server running. The Admin learned the hard way that Domino doesn't give warning messages for nothing, and that it's more restrictive than a bouncer at Studio 54 when it comes to access.
True Domino Blooper #26: Paper chase
This Domino developer found himself on a support call with a naive user. Find out what happens to our hero when someone can't differentiate between paper and electronic documents.
True Domino Blooper #27: Blame it on Domino
This Domino decoder has the familiar challenge of defending Domino to those who are too quick to blame it for unknown or idiotic end-user mistakes.
True Domino Blooper #28: The Super Server Upgrade
A member named Kent wishes his first name was Clark and he could fly around the world to reverse time in this True Domino Blooper.
True Domino Blooper #29: Agent OOPS
Here's a firsthand story from SearchDomino.com member Ann Eulert, who has definitely learned a lesson about creating agents. She offers an amusing story on her agent mishap, along with some useful, preventive code.
Do you have a blooper of your own you'd like to share? Tell us about it! Don't worry -- you can choose to remain anonymous.