Java Performance Services
Training, Seminars, Benchmarking, Tuning

Java Performance Tuning Course


Chania Crete, May 17-20, 2010


Sun Extreme Learning EXL-2025

Houston, December 1-4,2009
New York, December 8-11, 2009
Washington DC, January 5-8, 2010



San Francisco, January 11-14

Anti-if

I have joined Anti-IF Campaign

Calendar

««Nov 2009»»
SMTWTFS
1234
5
67
891011121314
15161718192021
22232425262728
2930

Performance Anti-Patterns

My Top Tags

                                       

Mailing List

My RSS Feeds








My grapple grommet isn't meshing with my filbert flange

posted Friday, 29 August 2008

After spending what seems like an eternity trying to configure this application to work with that application server and configuring that application server to work.... boy do I long for the old days.... the days when we just didn't have the hardware to support abstraction. There weren't any cycles to waste on silly things like flexibility. The days when if you were fitting your filbert flange with your grapple grommet, it fit perfectly because you didn't have any choice. Computers were the same. With no room for abstraction, you had to code everything.. and I do mean everything

But now everything comes pre-built. There isn't a lot of room for the average joe to do any real coding. All of that has been reduced to configuration. This leaves one to be looking at hundreds of configuration values scattered over dozens of configuration files typically burried in just as many sub-directories and WAR/EAR/JAR/RAR/....... and ..... files. Worse than trying to find all of these little buggers is trying to find out where they may (or most likely) may not be documented. Someone figured out that the filbert flange may want to go with a slightly different grapple grommet even though no one in their right minds would think of using a different grapple grommet. But, that is besides the point! We can make the system a little more fragile, a little more difficult to use and all we need to do is add a layer of abstraction and support it with yet more configuration values which we can hide in yet another configuration file. Who cares about the smuck trying to figure out wtf I was thinking at 3am in the morning when I came up with my moonstruck hairball abstraction that has more flexability than the under-aged chinese olympic gymnastic team. 

Think of it this way, we have all been reduced to coding in XML without the aid of debuggers and more often than not, with the aid of incorrect or incomprehensible documentation. A better grapple grommit that will mess with any filbert flange if anyone can figure out how to configure it.

And this is progress!