We fill the room with product experts and try to remove any barrier so you and your team can build the best application possible. 

  - clint

22 hours ago, Sven Groot wrote

@kettch: Yes, I'm following my life long dream of becoming a barista.

I'll take a 12oz double shot latte please

May not be your cup of tea but I couldn't imagine life now a days without my smart phone.  I've been on one since '05 too.

Also the connect site was back when we were going through the initial migration from v4 to rev9.

A lot of them are based on a reprap design as well.

I suggest checking out the software and how much tweaking you want to do to get it to print.  If your area has a makertareq like seattle's create matrix or tech shop, check those out as well?

Print bed size is another big thing.  I wish mine had a bigger bed almost right away.

Making the thing omatic was chances are one of the most confusing things ever.  Just put that in context with some of the things I have built . Took 2 days and chances are another 5 to get everything adjusted

Ultimately, what topics would you like to see covered? Also there are a lot of good tutorials out there on the internet. 

My best bit of advice is to figure out a project you want to do and start working on it.  I know doing projects for myself made me into a much better programmer for multiple reasons. 

• I did projects that I wanted to be awesome.  This meant everything worked and wasn't hacked together. 
• The projects I did challenged myself into having to do research.  Now you can throw me at something totally new and chances are, I can get up and going pretty quick by poking around.
• It is more enjoyable.  You build something you want.
• Getting your hands dirty.  The more you see how others do stuff and making mistakes, the better you get at being a better programmer.  It is like riding a bike or driving a car, the more you do it...

6 people in the field of vision is a lot, believe it or not.  Back with beta 1 and testing out tracking, having 4 people in my office was tight.

Have you played with the SDK?

I have on my blog my real time thoughts on building it out over a few months along with a post on Coding4Fun.  With that said, I don't know if I'd do it the same anymore.  That was built before things like netduino and arduino existed.

For Windows Phone 7, download links for everything are in:

http://channel9.msdn.com/Series/Windows-Phone-7-Development-for-Absolute-Beginners/Installing-Visual-Studio-2010-Express-for-Windows-Phone.  

Mango beta tooling:  http://www.microsoft.com/downloads/en/details.aspx?FamilyID=77586864-ab15-40e1-bc38-713a95a56a05&displaylang=en

For Day 1, Assignment 3 you could either open up HelloWorld.sln or HelloWorld.vbproj.

I'd suggest always using a solution file if it exists since a solution could have multiple projects in it.

Gadgeteer to me is more like a LEGO mindstorm, you plug in the sensor and it just works.  You lose a degree of flexibility but you gain speed along with reduce complexity in the prototype environment.