If this isn‘t an example of misdirected use of technology, then I am not sure what is? 
What prompts such an invention? Is there really a market for this? Who knows.
Anyway, if the guy forgets to do the laundry, will the dirty laundry keep piling up? Because, the machine is inoperable unless we alternate the user. So will she be left with more dirty laundry than usual?
From the article:
“Spain is changing a lot, and I wanted to come up with an invention to enable men to do more around the home.”
This ain‘t funny.
“Some men may disagree that it is a good present for Father‘s Day and argue that it is more of a gift for the lady of the house.”
Some men? Some? Men? I wonder which men agree it is a good Father‘s Day present. I hope this invention stays in Spain. 
My prediction: has excellent potential to become a relationship killer inducing more / faster break-ups. It‘s a Breakup Machine, Eh?
Humor
May 3rd, 2005
As I mentioned in my earlier post, I spend some of my time on building a rich UI application using Swing. And when it came to choosing a mechanism to store my user preferences, I decided to not use property files which was how I had stored preferences before. But, now (since Java 1.4) I use the java.util.Preferences API to store and retrieve my preferences. I would not store sensitive information in preferences, but for non-sensitive info, Preferences API is a great way to persist and manage them. The reason I am posting this is that while talking to some of my friends I realized that not many were aware of the Preferences API despite it being around for a while now. Perhaps because most of us have been focussed on server-side software where we have many other options to store preferences such as JNDI registry or a centralized configuration management system. Anyway, if you are building a stand-alone Java application or a rich client and have a need to store user preferences, take a look at the Preferences API. I think it is a cool API.
Some references:
Java Programming
May 2nd, 2005