Skip to main content

Product review: Anker RoboVac 10

This is a first. I have never done a product review on my blog. To head off questions, no I am not being paid for this. No, I did not receive this item as a sample or promotional item. Yes, I paid full price for it.

With that out of the way, Anker RoboVac 10 is an automatic self-docking robotic vacuum cleaner. Basically, it's a Roomba. But is a rose still a rose if it goes by a different name and costs far less? I don't know. Never had a Roomba but I bought this Anker RoboVac last week on Amazon and it arrived couple of days ago. Setup was quick and easy but the vacuum wasn't pre-charged (more on this later). So I charged it overnight, set it to clean at 7:30 am and forgot about it. At 7:30 the next morning, it very quietly went to work. While the kids ate breakfast, "Robby" (as my daughter christened it...yeah we have a habit of naming everything...I am typing this on Maggie4) cleaned 2 bedrooms, a dining area, a hallway and the kitchen. Robby was still cleaning when we left the house an hour later. When I got back after work, the house was spotless...you know that "maid came while we were gone" look? That's how the house looked. And Robby was back on the charging cradle ready for another day of thankless hard work sweeping up after humans.

Pros

  • Very quiet
  • For a $199 device, it magically finds it way to the charging base every time
  • Goes under pretty much anything: bed, couch etc
  • Call me crazy but I like the idea of turning it on, leaving the house and coming back to a clean house.
  • It cleans all floor types: carpet, hardwood etc.


Cons:

  • No battery life indicator
  • The scheduling doesn't handle anything but daily cleaning. I like a clean house but I don't want Robby cleaning every day
  • Apparently, the Roomba has features that lets you map out where the robot should clean. Robby doesn't have that feature. I just made sure to close doors to rooms I didn't want it to clean...like bathrooms and closets.
  • Replacement parts aren't available (yet). It does come with an 18-month warranty.

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…