Every week I get a compiled list of all the product feedback we have received during the week from users. A lot of it is complimentary which is great and I love to see it. Some if it is not. Some of the stuff that is not complimentary is fair. And some if it - well, if not exactly unfair - is the result of misconceptions about our InnerWorkings Developer product. Two misconceptions came to mind as I read through this week’s feedback:

1. We don’t teach syntax. We assume that you are a working developer, a practitioner. We don’t try to recreate the many resources and methods (classes, books, e-learning courses) that are available for beginners. There are so many great things out there at that level and, anyway, it isn’t really the issue we are interested in. We are VERY interested in the next stage and in the stages after that.

2. It’s not really about ‘passing’ the code judging engine. Of course, at one level it is, but that is not the really significant part. The point is to help you develop your capabilities (and career) by having you solve problems in Visual Studio as you do, day-to-day, on projects. The significant part is the work you do while working on those problems. The outcome is the validation (to yourself or to others) that you can apply the techniques appropriately and efficiently. Building higher levels of performance and problem-solving.

Irrespective of the feedback, we really like to get it. We give it a lot of attention so please keep it coming!

Add this post to: del.icio.us:Product Feedback digg:Product Feedback spurl:Product Feedback simpy:Product Feedback newsvine:Product Feedback blinklist:Product Feedback furl:Product Feedback reddit:Product Feedback Y!:Product Feedback google:Product Feedback technorati:Product Feedback stumbleupon:Product Feedback windowslive:Product Feedback