Ken, try not to take the negative criticism too much to heart. Scoble makes it look easy, and interviewing is not easy.
Some advice: 1. Keep your questions short and simple. The most common mistake rookie interviewers make is talking a lot. The interview is about the people being interviewed, not the interviewer. 2. Have some fallback questions. You shouldn't script all your questions, but if lulls develop, have something to ask to resume the flow of conversation. 3. Ask Scoble and other experienced interviewers for advice on interviewing.
I took a look at Erik and Paul's blogs. One of them mentioned not being able to cover XLINQ in these videos so maybe you could talk about XLINQ and VB.NET in a future video. Talk to Erik and Paul about topics that make sense to cover in future videos. They're
the domain experts, not you or me.
I guess the funny looks Paul and Erik shot you at some of your questions at the beginning of the interview gave me the impression that they thought the talk was going to be an advanced talk, too. Once you guys got on the same page though, the interview went
better. I viewed the video before the downloadable version was available so I couldn't skip ahead to the parts that interested me. That's no one's fault.
Check that for details on what is changing in VB.NET 9.0.
I (and many others, I'm sure) still haven't forgiven MS for what they did to VB 6.0 (or VB 3.0 for that matter), but I'm happy to see that VB.NET is getting closer to parity with C# on language features.
I feel like Windows Mail aka Outlook Express on Windows Vista is just another iteration rather than a revamp of what an e-mail client can be. Maybe I was expecting too much?
I appreciate MS taking the time to make Windows Mail as good or maybe a little better than Thunderbird, but I can't help but feel like there's a better way to write an e-mail client than having it be the next iteration of the GUI version of UNIX mail.
Maybe my expectations are too out there, but my version of "shock and awe" is probably different than other people's?
The changes they have made to VB.NET allow you to take advantage of dynamic programming without having to write a ton of System.Reflection code and turning Option Strict On or having to turn Option Strict Off.
Writing System.Reflection code and turning Option Strict On to do dynamic programming in VB.NET requires writing a lot of code every time you want to do something dynamic.
Turning Option Strict Off lets you do dynamic programming, but you lose the benefits of compilation, taking performance hits (runtime type resolution) and reducing the ability of the compiler to detect coding errors.
Oh and trying not to be rude here, but maybe next time have someone familiar with dynamic programming and VB.NET do the interview. That way, you can spend more time in the interview actually showing what improvements they made to the new version of VB.NET
to enable better dynamic programming and not spend so much time educating the interviewer on why it is important.
Unless that was the intention, in which case, ignore my advice. I guess I was expecting a 300/400- level video, not a 100/200- level one.
CDCer, the difference between Windows Vista and Mac OS Tiger is that more than 5% of the personal computing community will actually be using Windows Vista. Microsoft is bringing this technology to the people in that community who don't want to pay for overpriced
By itself, this is impressive, but combine this with WinFS and Web service classes... yeeow, the possibilities are staggering! No wonder they're so excited about this.
One quibble - when Anders was talking about the reason why the "from" clause had to be first, it made a lot of sense, but then I went to the VB 9.0 whitepaper and saw this:
Dim SmallCountries = Select Country _ From Country In Countries _ Where Country.Population < 1000000 For Each Country As Country In SmallCountries Console.WriteLine(Country.Name) Next
The VB.NET syntax for LINQ looks more like SQL than the C# syntax. However, Anders' point about the C# syntax being better for XML querying still holds and is demonstrated by this VB.NET 9 snippet later in the whitepaper:
Dim CountriesWithCapital As XElement = _ <Countries> <%= Select <Country Name=(Country.Name) Density=(Country.Population/Country.Area)> <Capital> <Name><%= City.Name %></Name> <Longitude><%= City.Longitude %></Longtitude> <Latitude><%= City.Latitude %></Latitude> </Capital> </Country> _ From Country In Countries, City In Capitals _ Where Country.Name = City.Country %> </Countries>
There's a lot of XML cruft before you get to the "from" and "where" of your LINQ code. It's easy to imagine how nasty it could get with a more complicated XML document. The C# syntax clumps all the LINQ syntax at the beginning and leaves the XML cruft for
By the way, note the ASP.NET-like syntax in VB.NET 9!