One graph per CPU

There are times when setting "One Task Per CPU" is not helpful ;-)

if you look carefully you can see that CPU 10 was busy at some point, this kind of screen shot raises the question of how are we going to understand application run-time behaviour when we have hundreds of CPUs...
source Mark Russinovich's "Pushing the Limits of Windows: Physical Memory"

Outlook tool for attachments doh!

How many times have you sent an email to someone with an attachment - which you then forgot to actually include the attachment?

The Missing Attachment Powertoy fixes this:

"Have you ever forgotten to include an attachment to an important email? Missing Attachment Powertoy integrates with Microsoft Outlook 2007 and scans each message before it is sent, looking for words or phrases that would normally indicate an attachment. If it finds such references but the message does not have an attachment, it brings up a dialog to alert you and gives you the option to revise the message before sending. You can customize the list of trigger words based on your personal email habits and words that you would commonly use when sending a file attachment. Simple and useful."

NASA gives some telling insights into software

An illuminating report by NASA "NASA Study on Flight Software Complexity" has much to offer people involved in software, be they programme manager, developer, tester, architect etc - I wish this was a book already! I'm seriously going to read the whole thing (even at 264pp) because even a one hour skim has given me so much already - truly a must read!

One of the most AMAZING things was, how many lines of code are in a GM car? when I saw the answer I had to get the rest of the team to answer the question - one of them could not even understand that there would be any lines of code in a GM car! check out the graph:

Yep, that's right, by 2010 there will 100 million lines of code in an average GM car - jaw dropping! how many bugs would you expect in 100 million? - now if GM build their code to the same level as NASA and other flight companies (good luck with that) then according to NASA (Appendix D)

"For the new manned space program we should probably expect close to 10 Million lines of flight code, and one to two orders of magnitude more ground software. If we go by industry statistics, a really good (but expensive) development process can reduce the number of flaws in software to in the order of 0.1 residual defects per one thousand lines written. A “residual defect,” for all clarity, is a defect that shows up after the code has been fully tested and delivered with an industry-standard rigorous testing process. A system with a million lines of code, then, should be expected to experience at least 100 defects while in operation. Not all these defects will show up at the same time of course, and not all of them will be equally damaging."

OMG - even if GM write aeronatics quality code then an average GM car in 2010 will have 10,000 defects. Now there's a reason to get into testing as a job ;-)