Chris Anderson, an architect on the Avalon team, talks about the history of the Avalon team, including how it was formed, the goals for Avalon and the rearchitecture a year before the PDC.
While things will most definately change before VS.NET Whidbey is released, this document provides a great list of new features in both C# Whidbey and VC# Whidbey. And it's much more than generics, partial types, anonymous methods and iterators.
[weblogs.asp.net/duncanma]
I was interviewed by John Kador yesterday about his upcoming book "How to Ace the Brainteaser Job Interview." At the end, he asked me for references to other folks that have had the experience of being asked or of asking brainteasers in interviews, so I'm posting his request:
I’m a Chicago-based business writer.
My upcoming career book for 2004 is called How to Ace the Brainteaser Job Interview. It will be published by McGraw-Hill. The book is designed to help applicants think strategically about the puzzles, riddles, business cases that they may encounter in today’s job interview.
I’m looking for examples of puzzles, riddles, brainteasers, etc. and how they are used in the job interview. I’d like to pepper the book with real-life anecdotes from people on both sides of the table. What puzzles do you like to ask and what do you look for? What are particularly elegant responses? From candidates, what questions were you asked and how did you handle them? Nothing will be attributed without permission. I’ll also be very generous with acknowledgments.
I welcome suggestions and questions at jkador@jkador.com. My web site is http://www.jkador.com.
John Kador
To save myself linking to nearly every single one of his posts, I'll just tell you now:
If you're doing WinFS or curious how it works or what it means, you *must* read Mike Deem’s blog.
If you haven't noticed, the Longhorn SDK site on MSDN [1] has a new area at the bottom of each page. We call the entries in this area "annotations." This area is broken up into three parts:
1. Microsoft "official" annotations, like what you'd find in a ReadMe, but associated with the specific piece of content itself
2. General group discussion, like in a newsgroup, but again, associated with the content itself
3. 3rd party annotations
The 3rd part come from a client-side component that acts as an RSS aggregator, pulling annotations for a specific piece of content from the RSS feeds that you subscribe to via the component.
O'Reilly was nice enough to provide an RSS feed at the launch of the annotations project to both demonstrate it's usefulness and provide real annotations to about 50 pieces of content on the Longhorn SDK. In addition, they've posted a nice article about how other 3rd parties can provide their own annotations via RSS to nestle at the bottom of the MS Longhorn SDK content.
If you'd like to provide annotations for folks to subscribe to as "annotations," you can do so without any permission or special support from MS. If you'd like to be considered as a "Recommend" source of annotations, drop me an email: csells@microsoft.com.
[1] http://longhorn.msdn.microsoft.com
Normally I wouldn't point this page out, because it's *unofficial* and *unsupported*, but some folks have used the guidance on this page to fix issues with the PDC Longhorn bits, especially as related to networking. USE AT YOUR OWN RISK.
Under Whidbey, VC++ supports both CLR generics and C++ templates for managed code. In this post, Brandon Bray, a PM on the VC++ team, lays out the differences, while also laying out the differences between C++ templates and CLR generics in general.
