Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

r_keith_hill

r_keith_hill r_keith_hill ktm250

Niner since 2004

Grew up in Kentucky, graduated with a BSEE from Vanderbilt University in '86. Got a MS in Computer Engineering from CU Boulder in '96. Been working for Hewlett-Packard, now Agilent since 1986 in Loveland, CO.
  • Pat Helland - Sings Bye Bye to Mr CIO Guy

    Bravo! Bravo!  That takes big cahones.  Those kind of ideas either really go off big or bomb big time.  Well done.
  • Chris Brumme - How about a type-specific try-catch mechanism for Intellisense?

    I haven't use Java however I can see that checked exceptions might be a bit too much of a versioning hassle.  OTOH the concept does appeal to my meticulous side.  I think the concept of a non-enforced checked exception (perhaps a better name is "documented exceptions") is a good idea.  I have run into exceptions in shipping code that weren't documented in the MSDN docs!  So even though I thought I was handling everything, I wasn't. And the real drag of it all was that it wasn't a fatal exception.  It was something, that if I had caught it I could have put a message to the user that they needed to re-install/repair in order to use a particular feature. I am also intrigued by the concept of slicing exceptions in a different fashion besides inheritance hierarchy. I have always thought the .NET exception hierarchy could be better.  There are some exceptions that inherit directly from System.Exception. Other inherit from the vestigial System.ApplicationException. And worse, it is not easy to tell which exceptions should only be thrown by the runtime like System.NullReferenceException or System.IndexOutOfRangeException. I still occassionally catch folks throwing those exceptions rather than the ones deriving from System.ArgumentException. Perhaps all the runtime exceptions should implement an attribute or marker interface like IFatalException or IRuntimeError or something like that.

  • Anders Hejlsberg - Tour through computing industry history at the Microsoft Museum

    I got the chance to tell Anders this at the PDC which was cool.  In '85 a couple of my buddies and I worked in a PC lab on campus. In our Pascal course, we managed to convince the teacher to let us do our projects on PCs using Turbo Pascal.  The rest of the class used the campus mainframe (Cyber something or other) with a crappy line editor and I'm not even sure what they used for a debugger (printf equiv?). Anyway, we smoked the rest of the class.  The teacher was quite impressed with how quickly we finished our projects and the quality of the code.