Today I'm wearing my QA hat. While testing out the search function in the demo (aka Project Alameda) we are building for JavaOne, I found The Kitchen Sink Language. I'm assuming this guy is not serious, mixing functional and object oriented programming like that. Getting on my soapbox for a moment, I think the choice of technology rarely completely breaks the project, its getting the requirements right in the first place that really counts. The problem is that non-techies seem not be able to visualize how a software application might work nor do they think in linear, decision tree fashion. So what you do, build prototypes, maybe more than one, and feel free to throw it away and change the platform/language underneath if you think it's needed. I will say however, that the choice of technology (not to mention a decent architecture) often becomes more important the longer lived the thing is. It's a often lot easier to get something out the door than to maintain and enhance it well. Or maybe that's just my perspective, since I seem to end up keeping someone's opus functional. Off soapbox.
Lots of JavaOne buzz and activity. I'm working mainly from home this week (I'm one of those "flex" employees) and I'm even catching it from here. I talked to Tony (his blog) that is helping out, they are doing the heavy lifting today and getting all the machines into the pods. You've probably caught this elsewhere but check out: Java bloggers at Thirsty Bear. Thirsty Bear is a favorite watering hole, decent beer and great tapas, too bad I have a previous commitment. Also check out the Looking Glass Community meeting, no badge needed for entry.
