darrellp

I'm sorry to have sounded a little harsh, but as constructive criticism, I really never found myself looking at the screen and wondering about what the commentators were doing at that particular moment.  If nothing were going on with the screen and the commentators were addressing the camera, it makes sense to cut back, but as long as they're doing nothing more than staring at the laptop and something is being typed on the screen, I really don't see any reason or interest in cutting away from the screen and devoting a third of the video to a static image of them staring at the screen seems like overkill to me.  Just my two cents, and sorry again about sounding harsh.  Sometimes I slip into "sarcastic" without even meaning to.

Very cool idea and thank goodness somebody realized that there needs to be an insert row/column for grids (when is this going into Blend?).  Looks like it was really well executed, too, so thanks for all of that.

On the other hand, I think that whoever edited the video needs to understand that there is zero interest in watching two guys staring at a laptop, and FAR more interest in what is actually going on in the screen of that laptop.  After the typing began and before the final "goodbyes", I was extremely frustrated as he did who knows what to actually create the XAML because I was looking at him talking about it rather than the screen when that occurred.  Ditto for lots of other key points in the demo.  There was never a point where I was really curious about what it looked like to see them talking, so keep the camera on the screen please.

This looks really interesting, but obviously can only work to a point due to undecidability constraints.  So how sophisticated does it get?  If I have in my code:

if (SeventhOrderPolynomial(x) < 0)...

will Pex actually try to solve the polynomial and put in values of x where it is larger than zero and others where it is smaller?  Does it give up at a certain order?  Linear?  Diophontine equations?  Does it use some sort of Monte Carlo algorithm to guess at values which may or may produce different branches in the code?

I'm impressed regardless.  Very nice work.

Okay, I hate to be dense, but this is the first time in my life I've seen a "humanized screencast" or heard of a "high quality WMV download".  When I try running this regularly it constantly stops and reloads.  So it's lovely to know that it's best to view it in this new way but it would be lovelier if I knew what I needed to do in order to view it with a "high quality WMV download" whatever that is.  Sadly, while several of your videos on Ch9 suggest this, none of them offers anything in the way of instruction on exactly how to get such a thing.  Can anybody please bother to provide me with that info?  Thanks!