This was a last minute thing that came up, but yesterday morning I presented a 1-hour session on Team System to this virtual conference. I understand that they had 4500+ attendees signed-up. I know that my session had 100 people in it, which is great for a conference that was devoid of any specific tools (most topics were on management, theory, and best practice).
(Click to expand)
If you haven't played with the new Code Snippets features in Visual Studio 2005, you're missing out! It makes it easy to keep an entire library of useful code snippets within Visual Studio 2005, and at the ready to help with any programming assignment. Integrated Intellisense invokes them automatically.
In anticipation of this feature, my fellow RD J. Michael Palermo IV has created www.gotcodesnippets.net which will become the uber repository of such snippets. It will launch officially at PDC. 
Focused primarily on the Europe, Middle East, and Africa (EMEA) developer communities, the beta experience contains the latest news, free resources, training, and a free newsletter. Note: You won't find United States in the dropdown list, so try United Kingdom.
Besides the main launch event in San Francisco, on November 7, there are a few others in the West. Please feel free to register using code: LaunchTour2005.
Tuesday, December 6
Colorado Convention Center
700 14th Street
Denver, CO. 80202
303-228-8000
Tuesday, December 6
Anaheim Convention Center
800 W. Katella Ave.
Anaheim, CA. 90802
714-765-8950
Rich, my business partner and coblogger (his personal blog is here), is presenting a full day on Visual Studio Team System at the Wintellect Devscovery seminar at Microsoft. Great presentation that follows a development lifecycle all the way from Project Manager creation, to Architecture design, to Development and Testing. All the major roles and technologies are covered. Fun stuff!
Listening to Jeff Richter talk about Application Domain and Remoting. He's a good presenter, and very fun to listen to! Lot's of energy, but more importantly, very knowledgeable! I have a weakness for low level computer details (compiler details, behind the scenes optimizations, etc), and Jeff has tons of great nuggets! For instance, the ThreadAbortException is rethrown by the runtime, even if it is caught! In order to stop this, you need to call the ResetAbort() method, which requires certain permissions. Great use! This allows us to load possibly malicious code into an app domain with restricted permission, then any malicious code can't swallow an aborted thread, and continue to consume resources. Cool. See? Neat stuff! If you haven't seen Richter speak, or read one of his books, I recommend it!
Up front: I believe that Lines of Code is a USELESS metric. However, people are often shocked by the raw number of lines of code that are written each day by a developer. What's your guess? 1,000? 200? Try just under 20. This is basically the number of lines of code in a released project divided by the number of programmer days, so, just because you can write 1,000 buggy lines of code per day, that doesn't make you productive!  It's the post bug-fix, post integration testing, post-everything lines that count. (You can find some background here and here.)
Every time I show the show off the wonderful reports that are automatically generated by Team Foundation Server, I usually get asked about the Code Churn report, and what Code Churn is. After months of giving a good, but unofficial definition, Dave Bost, on his blog, did the hard work and discovered a wonderful (but academic) whitepaper on the Code Churn technology used by Microsoft in VSTS. The PDF can be found at Microsoft Research. It's called Use of Relative Code Churn Measures to Predict System Defect Density, by Nachiappan Nagappan; Thomas Ball. Here's the abstract:
Software systems evolve over time due to changes in requirements, optimization of code, fixes for security and reliability bugs etc. Code churn, which measures the changes made to a component over a period of time, quantifies the extent of this change. We present a technique for early prediction of system defect density using a set of relative code churn measures that relate the amount of churn to other variables such as component size and the temporal extent of churn. Using statistical regression models, we show that while absolute measures of code churn are poor predictors of defect density, our set of relative measures of code churn is highly predictive of defect density. A case study performed on Windows Server 2003 indicates the validity of the relative code churn measures as early indicators of system defect density. Furthermore, our code churn metric suite is able to discriminate between fault and not fault-prone binaries with an accuracy of 89.0 percent.
It's my math background... But I just have to post this!
Google is offering 14,159,265 shares of stock. That's the first 8 digits of the decimal expansion of Pi. Cool.
|
Copyright © 2010 Richard Hundhausen. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme:
|
|