Wednesday, December 03, 2008

Reply to SciAm Perspective: After the Crash

In the December 2008 issue of Scientific American, the editors wrote a SciAm Perspectives piece entitled “After the Crash,” that focused on making sure that some of the blame for the Wall Street crash is placed on the developers of the software models. The last sentence of the opinion piece really drives home how little the SciAm editors understand about the software models, “Like an airplane, financial models can never be allowed to fly solo.”

What?! The problem wasn’t that the financial models were allowed to “fly solo”. The problem was that the models kept getting changed to appease the developers’ bosses. The SciAm editors also try to make it sound like the developers should have just not made the changes to the models each time “overoptimistic assumptions and faulty data” was given. What should have they done? Just said, “I’m sorry, Dave. I’m afraid I can’t do that.” They would have been fired and then replaced. In some cases maybe they could make a stand and say that making the change is risky and shouldn’t be done without being fired. However, it would amount to the same efforts that Roger Boisjoly made on January 27, 1986, when he convinced his manager, McDonald, to warn the NASA managers not to launch the space shuttle, Challenger, until warmer weather. The push back from the bosses was such that another person was found to sign off on the launch.

I am getting a little off topic. Let us return to this financial airplane that we don’t want to allow to fly solo. Many disasters have been caused by people doing their best to “fix” the problem instead of allowing the established protocols (usually designed using mathematical models) to deal with the problem. I’ll give two examples: Three Mile Island and the incident aboard the drill rig Ocean Ranger in February 1982.

In short, it is wrong to blame the people who work on the product because they are not the people with the power to decide what work is done on the product regardless if the product is a car or a financial model.

Saturday, August 23, 2008

Bucket List

Get SCUBA certified: https://www.diventures.com/scuba/dive-certification-costs

Go on an Insight cruise: http://www.insightcruises.com/



Winchester Palace, London, UK

November 2, 2017 - Riverside remains of a 13th-century bishops' complex with ruins of great hall, prison and brewhouse. https://www.english-heritage.org.uk/visit/places/winchester-palace

Jerry Yoakum photoed in front of the ruins of Winchester Palace in London, England.

Saturday, February 23, 2008

Donald Knuth

Dr. Dobb's Journal published an Interview with Donald Knuth in April of 1996. It was a very good read.

Knuth discusses what distinguishes a "computer scientist" from a "computer programmer" but neatly side steps actually separating the two terms. Choosing to instead explain how computer science is about thinking about problems in a different way. (You'll have to ready the article to see what I mean.)

There is some discussion about Knuth's The Art of Computer Programming. Which Charles Moss tells me is a wonderful read. I'm not sure I believe that but the MSU library has volumes 1-3 in case I want to check them out.

I must quote this because one of my coworkers is just fanitical about C++. To him, everything that is not C++ is crap with the exception of javascript and ruby.

DDJ: You've mentioned Edsgar Dijkstra. What do you think of his work? DK: His great strength is that he is uncompromising. It would make him physically ill to think of programming in C++.


Kunth followed that quote up with some very reassuring comments about trying to find the middle ground between very specific control of code and allowing a library to be used without knowing how it was implemented.

[W]hen you write a program, think of it primarily as a work of literature. You're trying to write something that human beings are going to read. Don't think of it primarily as something a computer is going to follow. The more effective you are at making your program readable, the more effective it's going to be: You'll understand it today, you'll understand it next week, and your successors who are going to maintain and modify it will understand it.

Saturday, January 26, 2008

DVD-RW driver problem in Windows Vista

Something I installed in the past month made Vista no longer recongize my DVD-RW. I tried removing it and reinstalling it but that didn't work. After a few online searches I found "Top Tip: DVD-RW driver problem in Windows Vista?".

I don't know why it works or what application made my DVD-RW stop working, but Andy2639's solution works.

In case that URL is broken in the future here is the solution:

Open the Registry Editor, navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class
select key {4D36E965-E325-11CE-BFC1-08002BE10318} (now's a good time to backup)
delete the LowerFilters string value
delete the UpperFilters string value
Restart Windows.