The BEST way to learn about robotics is to study it in fictional media.
Pick up Star Trek, and study the cyborg known as Data. Pay attention to the Borg, and trace what little clues are there in their origin. Pick up Doctor Who and look at the Cybermen and Daleks, and pay attention to why the Doctor's always at war with them.
Pick up the movie "Terminator" and study the interactions the robots have.
Look at Elbot (http://elbot_e.csoica.artificial-solutions.com/), and Cleverbot, and pay attention to the similarities in the information acquisition, the discontinuities both exhibit, and the vocabularies (here: http://www.cleverbot.com/ [cleverbot.com])
Your computer, the one you are sending this request to, is a rudimentary robot. It includes peripherals which provide the computer stimulus in digitally interpreted fashion. Fictional media resources feature robotics which acts in a very predictable fashion, there's no spontaneity, the actions are guided, and there teds to be responses in reactive form to external stimulus received in highly predictable fashions.
So my advice is - before you go and get the Microsoft Robotics SDK or anyone else's interpretation of robotics, then study the core Microsoft Windows operating system at a messaging and routing perspective. Specifically: the WM_ messages and ask yourself - how are devices which 'come online' notified system wide?
What you're going to find is: software vendors have a habit of detaching you, the developer, by building in object layers and layers of abstraction away from the physical events themselves, but Windows - from the ground up - was actually built FOR robotics based on a messaging system and adoption of new peripheral devices that would be built, later, and applications developed for them once the device came online and found widespread use.
Take up Microsoft Visual Studio - C++ for a direct and easy to manage message pump and study they effects in the message pump when devices are brought online. My advice is to pull down Visual Studio 2005 or 2008, both of which Microsoft distributes as torrents if you can't afford it here: https://kat.cr/usearch/microso... [kat.cr]
Now be careful. Other languages such as Java, Python and ;NET may offer SOME semblance of message pump handling, but it's abstracted away from the hardware layer through volatile assemblies which have seen a ton of problems with compatibility and mismanagement of memory, not to mention it's not nearly as fast as managing the message pump yourself.
Now what's this all have to do with robotics?
If you study media, you understand where civilization is going and what - hardware wise - we have in store for our future. There's no 'quick and dirty' solution to robotics programming, the software is already all available out there, you just gotta learn how to learn about it and leverage it for yourself.
And thats where practice, practice, practice comes in.
And a few expenditures.You aren't gonna be able to get by this in the end.