When
· Naughties
· · 2005
· · · June
· · · · 09 (6 entries)

The Autobox of Death · Hm­m, maybe I should have an­oth­er blog for Ja­va geek­ing. What hap­pened was, I had an ArrayList<String> and for a va­ri­ety of rea­sons I de­cid­ed to turn it in­to a HashMap<String,String>. After I’d fixed ev­ery­thing up, I got the weird­est Nul­lPoin­t­erEx­cep­tion, and I traced it to a call that looked like (x is the HashMap)
if ((x.­size() > 0) && x.get(0).e­qual­s(­foo))
and some­how the com­pil­er had de­cid­ed that get(0) was a rea­son­able thing to do to a HashMap<String,String>. Uh, strong typ­ing, any­one?

 
COOL BIZ · Via NoniWe­blog, a point­er to the un­sur­pris­ing fact that Ja­panese busi­ness­peo­ple are dis­cov­er­ing the virtues of not wear­ing a tie; if you’ve ev­er been to work in a Tokyo sum­mer you’ll un­der­stand why this is a good thing. But, in a unique­ly Ja­panese way, they’re not just do­ing it, they’re mount­ing an of­fi­cial government-backed cam­paign. But most­ly I wrote this so I could slip in a point­er to this pic­ture.
 
Down & Out in Tulsa · If it seemed like on­go­ing wasn’t there, it wasn’t. My host has a dire tale of cas­cad­ing fail­ure, but the weird thing is, when the site was down, tracer­oute showed the pack­ets cas­cad­ing in­to Wil­liams Com­mu­ni­ca­tion, where they strug­gled from Pa­lo Al­to to San­ta Clara to Den­ver to Dal­las to dusty death in Tul­sa, Ok­la­homa. How un­for­tu­nate.
 
Royals 8, Giants 1 · We took in the game Tues­day night; here are some notes on the oc­ca­sion, a nice pic­ture of the ball­park, and a rec­om­men­da­tion for an on­line tick­et sell­er ...
 
NetBeans Notes · Item: For those of you who mi­grat­ed from Emac­s, you can eas­i­ly teach NetBeans control-F/B/N/P/U/D: go to Tools - Op­tions - Edi­tor Set­tings - Glob­al Key Bind­ings. Huge time-saver, and this should be the de­fault on OS X, since ba­si­cal­ly ev­ery oth­er text con­trol has those bind­ings wired in. Item: I up­grad­ed all at once to OS X 1.4, and Ja­va 1.5, and NB 4.1 (from a re­lease can­di­date), and a lot of JXTA li­braries, and things are slow­ing down. I don’t like this; in par­tic­u­lar I hit control-space for au­to­com­plete or F9 for com­pile and it some­times has to think for a sec­ond first, which is nut­s. [Up­date: Fixed it! I had stupid­ly put all the sup­port li­braries that JXTA needs to run in­to the compile-time list, so they were go­ing on the class­path. Take ’em all out and it’s back to near­ly in­stan­t.] Item: Pro­ject Coy­ote is com­ing along nice­ly, and it’s in­creas­ing­ly ob­vi­ous that dy­nam­ic lan­guages on the JVM are go­ing to be huge. Item: NetBeans Day at Ja­va One looks like it’ll be se­ri­ous fun. Item: (This is not NB-specific.) When I go grab a new API, it’s just way too much work to tell the IDE about it and get the jars and Javadocs in place. There ought to be a stan­dard way to pack­age a Ja­va API so that you can point your IDE at some URI and it Al­l. Just. Hap­pen­s. Item: Here’s a nice fea­ture, does any IDE have it? When I say
Zig­garut z = new Zig­garut(brick­s, stones);
then the IDE should fig­ure out that that’s a com.­tex­tu­al­i­ty.3d.Zig­garut and in­sert the ap­pro­pri­ate im­port state­ments for me, it’s a to­tal waste of time for me to go pok­ing around try­ing to re­mem­ber where that was. [Oop­s: NetBeans has “Fix imports”, Eclipse is pro-active about sug­gest­ing it, and the IDEA cult as­sured me (as usu­al) that they have some­thing even bet­ter.]

 
On Time · Its ex­tent is fixed, in­elas­tic. Some of the time you spend leaves a mark on the world, some not. Some is plea­sur­able, some not. Some is nec­es­sary, some not. The waste of time is the on­ly waste that is ir­recov­er­able, even in prin­ci­ple. But you got­ta slack off some­times or you’ll go nut­s.
 
author · Dad · software · colophon · rights
Random image, linked to its containing fragment

By .

I am an employee
of Amazon.com, but
the opinions expressed here
are my own, and no other party
necessarily agrees with them.

A full disclosure of my
professional interests is
on the author page.