<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Well, it is that time again:  Reviews!</title><link>http://blogs.msdn.com/brada/archive/2004/06/22/163157.aspx</link><description>ChrisAn posted about the process in general last year , so I will not bore you with it. But one of the things I do as a manager is talk to people that my team has interacted with over the period and get their feedback. This time the specific question</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Well, it is that time again:  Reviews!</title><link>http://blogs.msdn.com/brada/archive/2004/06/22/163157.aspx#164444</link><pubDate>Thu, 24 Jun 2004 06:59:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:164444</guid><dc:creator>Adam</dc:creator><description>&lt;br&gt;I'm waiting for the first blogger to suggest that we should let the development community choose when we go to the bathroom.&lt;br&gt;&lt;br&gt;Is there no internal process that doesn't benefit from &amp;quot;community involvement&amp;quot;?</description></item><item><title>re: Well, it is that time again:  Reviews!</title><link>http://blogs.msdn.com/brada/archive/2004/06/22/163157.aspx#166252</link><pubDate>Fri, 25 Jun 2004 20:01:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:166252</guid><dc:creator>Keith Hill</dc:creator><description>I have found your blog along with other Microsoft employee blogs (Chris Sells, Krzysztof Cwalina, Chris Brumme, Eric Gunnerson, Scobleizer, etc) to be very informative and useful. I especially like seeing early versions of what you're thinking about for new Class Library design guidelines and for VS 2005 and Longhorn.  WRT the updated design guideline tips, I can apply many of those today. I'm also glad to have been made aware about certain pitfalls in MS software such as the serialization issues with System.DateTime. &lt;br&gt;&lt;br&gt;In general I think MS is doing a good job WRT to the &amp;quot;Law of Candor&amp;quot; (from The 22 Immutable Laws of Marketing) on these blogs.  After all, your customer on these blogs are also developers and we can appreciate how difficult it is to get software right.  By admitting to mistakes and helping us deal with those mistakes, I think you build more credibility than you'd lose by glossing over the mistakes.  Finally, I think it is great that most of the blogs allow for comments (customer feedback). It feels good that someone at Microsoft is listening to your suggestions. I think Microsoft products could wind up being better as a result.  OTOH, I would issue the standard caution about small sample sizes. :-)</description></item><item><title>re: Well, it is that time again:  Reviews!</title><link>http://blogs.msdn.com/brada/archive/2004/06/22/163157.aspx#167864</link><pubDate>Mon, 28 Jun 2004 15:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:167864</guid><dc:creator>JD</dc:creator><description>Krzysztof rules! Seriously the work he put into the Guidelines and his earlier work with streamlining things like event tracing are great.&lt;br&gt;&lt;br&gt;I don't know Kit's work as well but he seems to be on top of things. &lt;br&gt;&lt;br&gt;I don't know Joe unfortunately.&lt;br&gt;&lt;br&gt;Do you provide feedback for other people's reviews? Those who have helped you through the year?</description></item></channel></rss>