In the past, we have relied on internal dogfooding, external alphas and betas, and usability studies of work-in-progress to get feedback that can be used to improve the feature before being released to the public. We are still doing that more than ever. However, blogging has opened up a new channel of feedback that I'd like to take advantage of.
As you may or may not know, I am a developer for the Visual Studio debugger, with a strong emphasis on the user-interface the debugger presents. That being the case, I am keenly interested in hearing about what you love about the debugger, what you hate about it, and/or ways you think it can be improved or changed to better meet your debugging needs. As posts are made, I will not only note the feedback and try to address it in future versions, but I (and others who read this) will be sure to post guidance and/or tips to help address your needs with existing versions of the product.
To get you started thinking about it, I'll pose a few questions:
And here are a few usability tips:
While your at it, also be sure to check out some of the other blogs here that address our debugger, including: http://blogs.msdn.com/stevejs and http://blogs.msdn.com/greggm.