Excellent work guys. C9 has become an awesome resource. To me the ice breaker content is perfect (opposed to demo-hell at silverlight.net), but the deeper 'going deep' style needs a little more... depth. The content is always good, but it might not
be what the community would really like to know. In spirit of helping or targeting the community more, maybe its a good idea to open some form of dialog to the videos?
There are a few possibly good options I see for that. One way would be to put up a new form or method of seeing upcoming videos and with key topic points. Through this, allow user feedback/questions before the video is recorded. Another simply way may be
quick follow up interviews to interesting questions submitted by users? The third way is similar to the second, but instead of a followup interview, provide some answers through 'This Week on C9'. Allowing this sort of participation in the content will greately
I'm not sure if this is the proper place for them but I thought I'd add this in. Heres an idea for a show I'd like to see made:
General mistakes and optimizations for .Net developers -- E.g. .Net/BCL features people often ignore but could be helpful? .Net/BCL features commonly used incorrectly? .Net/BCL usage mistakes causing slowness or circumvent compiler optimizations? .Net/BCL
optimization and tips not covered in best practices.
Thanks for the feedback, pdev. I like the idea of getting more Niner participation in the interview process. We're always looking for suggestions on who to interview and what topics to cover. This forum is the right place for this. In terms of having you
provide questions prior to interviews, we've done this before and will continue to do it. In many cases, however, we don't have much turn around time for our interviews which means they are scheduled and shot in a few days, sometimes in one day. What would
be great would be a twitter-like feed that the interviewer could monitor during the interview, basically a virtual "call-in" mechanism in real time. We are looking into this.
Keep the feedback coming! C
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.