But good topic...
Automated stress testing of Office apps would be interesting to learn about like Word, Excel and Visual Studio, etc.
Loading user information from Channel 9
Something went wrong getting user information from Channel 9
Loading user information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
|Coffeehouse||New video topic I would like to see touched on||0||Nov 09, 2006 at 9:38AM|
|Coffeehouse||Does a fact is a fact.||20||Nov 03, 2006 at 10:18PM|
... we have powerfull corporations and their Product Branding and Marketting teams (with good intentions) bastardizing the basic rules of standardized and simple English sentence structure.
I love the DOT-NET technology, but the DOT-NET product branding is destroying the written form and use of the english language in the technical journals.
Here is an example sentence from the Editor's Note of MSDN Magazine, Paragraph 2 - sentence 2, April 2004 Vol 19 NO 4
"Leading off, we'll explain to you the fundamentals of code coverage in .NET. Code coverage is a way to make sure that all parts of your application are tested propertly -- it doesn't determine that they work properly, just hat they're covered by your test suite."
The above use of '.NET.' basically invalidates ALL of Bill Hills arguements.
We already have _exceptions_ to the rules with 126.96.36.199 version numbers embedded in sentences.. now we have sentences STARTING with periods preceding Nouns. ;(
This is one reason why Homo Sapiens will never evolve beyond version 1.0.