Feeling sort of human, again 
2011.01.09 13:23 - Work-related
As I write this, the other computer is logged into the office, on the likely chance that work will call again, today. Whee.

But, other than that, I'm feeling pretty fair. Two weeks of vacation at the end of the old year will do that for you.
  |  [ 0 trackbacks ]   |  permalink
Not dead, just tired 
2010.11.30 20:24 - Entertainment, Books, Movies, Meatspace Stupidity, Whining, Work-related
Criminy, it's almost December.

I think I can sum up my life the last month as: work, TV zombies, work, TV spies, work, TV spaceship, work, work, cartoons, more cartoons, minecraft, work, TV zombies, work, etc.

I've read Monster Hunter Vendetta, am most of the way through Unseen Academicals, watched a movie or two, eaten some turkey, and have otherwise been a little too shelled from work to devote much time to life outside my head.

Two and a half more weeks to the end of the year, for me. I think I owe my employer two-hundred-odd unit tests and some additional code in the meantime, though.

Oh, and I've been listening to The Protomen. First album's okay, second's very good.
  |  [ 0 trackbacks ]   |  permalink
I wonder if there is special significance in Chicago? 
2010.10.19 09:53 - News and Politics
I just noticed that Election Day is the same day as Día de los Muertos this year.
  |  [ 0 trackbacks ]   |  permalink
Wow. October, Huh? 
2010.10.12 16:00 - Guns, Internet Stupidity, Meatspace Stupidity, Toys, Actual Toys, Work-related
It's been a few days since I posted anything here.

Work-wise, I've been tied up in a release that's finally coming to a head ... about an hour from now.

Outside of work, RHIT homecoming has come and gone. Related to that, Verizon has been bugging me. It seems I have some charges on my next bill for text messages. I sent or received some 40-odd messages trying to stay abreast of doings in the Haute.

Related: Legos are expensive, but I think I won the trip to Toys R Us. (Go me?)

Also noticed: guy in the pawn shop with a GPS ankle bracelet. I'm guessing a restraining order was involved, because he didn't seem to be under house arrest.

I seem to have picked up some sort of infection in the Haute or just before or after, and took almost long enough to get my butt to the doctor for things to become serious. Fortunately, they aren't, and time plus amoxycillin cures many a post-nasal drip. (Related: Zyrtec-D is fantastic.)

As far as things not related to bodily fluids are concerned, I got out to Knob Creek the last weekend of September, and mostly proved I'm so out of practice that I've forgotten what I'm doing (hammer bite!). A few trips to Open Range will work out some of the kinks, pistol-wise, but that just means I'll be back on the paper. And I need to build a target stand before I go back to KCR. The rentable stands weren't much three years ago, and they're even less now, regrettably.
  |  [ 0 trackbacks ]   |  permalink
Other People Should Make My Life Easier 
2010.08.27 09:29 - Entertainment, Microcode, Whining, Work-related
I'd like to be able to do something like this
try {
    /* and then, a miracle occurs! */
} catch (BarException beFoo => String.Equals(be.Property, "Foo")) {
    // foo handler
} catch (BarException beBar => String.Equal(be.Property, "Bar")) {
    // bar handler
} catch (BarException be) {
    // general BarException handler
}
Mostly because it seems slightly cleaner than the current approach to handling, e. g., OracleExceptions, where one might care about some of the error codes represented by the exception, but not all of them:
try {
    /* and then, a miracle occurs! */
} catch (BarException be) {
    if (String.Equals(be.Property, "Foo")) {
    // foo handler
    } else if (String.Equals(be.Property, "Bar")) {
    // bar handler
    } else {
    // general BarException handler
    }
}
Some flexibility is lost vs. using if-else statements instead, but you could produce the same thing with typeof and nobody sane does that if they can get out of it, either. Semantically, it's pretty much equivalent and, syntactically, it's more verbose (to no obvious semantic advantage), so I'm sure it's not actually a good idea. (Additional evidence it's a bad idea: I'm sure I'm not the first to hit on this idea, yet it isn't implement in C# as far as I can tell. Presumably, those guys know what they're doing.)

Granted, it would be even better if Oracle would throw different exception types for different error codes instead of throwing the one type with slightly different data, but some problems seem, prima facie, less intractable than others.
  |  [ 0 trackbacks ]   |  permalink

Back Next