Jay McGavren's Journal

Diana tolerates the following things on a daily basis that only my immediate family and closest friends can (and then only occasionally), and I love her for it:

my squeaky-voiced impressions my digital photography (which consists of snapping 50 jillion shots, often unposed, in hopes of getting a few good ones) my bizarre sense of humor my long-limbed klutziness

….there’s more, but that’s what comes to mind for now. .

Diana likes the following things that only a male japanophile nerd would normally like, and I love her for it:

sushi Tivo Mahou Tsukai Tai! HD television Soul Calibur Dead or Alive Halo Tetris Attack Tenchi Muyo! Howl’s Moving Castle digital photography

….there’s more, but that’s what comes to mind for now. .

DRuby has me thinking...

All a developer should have to worry about is coding his API and maybe his user interface. Networking, permissions, input, rendering to the screen - all of that should be taken care of for him. He shouldn’t need to worry about whether an object will be accessed from a PC, a cell phone, or a dumb terminal on the other side of the world.Because the moment he does worry about any of these things, the solution he comes up with is gonna be “wrong” from someone’s perspective.

The MOO mini-cards came last night; they’re gorgeous. They were no effort at all to create, too. Kinda made me forget that I was dropping $20 plus $5 shipping on something I have no practical way to display or carry in my wallet. They don’t make frames for something that’s half the size of a business card.

They’ll probably wind up sitting in their box on the end-table, waiting for guests to flip through them and take one. They point to mcgavren.com on the back, so once I actually have a page up there, they’ll be able to see all the rest of our photos.

.

Extract local variable...

Eclipse just saved me a couple hours’ work… Thanks to a series of admittedly bad decisions, I had a unit test chock full of call chains like this:

assertEquals("West", hc.getAreaInfo().getAttractions().getAttraction().get(3).getRefPoints().getRefPoint().get(0).getDirection());
assertEquals("Name", hc.getAreaInfo().getAttractions().getAttraction().get(3).getRefPoints().getRefPoint().get(0).getName());
assertEquals("20",   hc.getAreaInfo().getAttractions().getAttraction().get(3).getRefPoints().getRefPoint().get(0).getTransportations().getTransportation().get(0).getTransportationCode());
//...etc

….too embarrassing to let a colleague see. So I was resigned to spending a very boring midday importing the appropriate classes and assigning those values to local variables, when it occurred to me to check Eclipse’s Refactor menu…

And there I found “Extract local variable”. What a godsend. All I had to do was highlight the section of the call chain I wanted, and it (intelligently) chose a variable name, replaced all occurrences with the variable, and even imported the classes I needed. In just a few minutes the above code and everything like it was changed to this:

com.mycompany.ota.generated.AreaInfoType.Attractions.Attraction attraction = hc.getAreaInfo().getAttractions().getAttraction().get(3);
RefPoint refPoint = attraction.getRefPoints().getRefPoint().get(0);
assertEquals("West", refPoint.getDirection());
assertEquals("Name", refPoint.getName());
assertEquals("20",   refPoint.getTransportations().getTransportation().get(0).getTransportationCode());
//...etc

Java is a very bad language, and Eclipse is what was created to cope with it. Fortunately, its creators exhibit boundless ingenuity.