http://www.theserverside.com/news/thread.tss?thread_id=22885#104396
Насколько ето все правда? Может просто товарищ слишком нервныи
Heh
Posted By: Cristian Golumbovici on December 17, 2003 @ 09:35 AM in response to Message #104396 3 replies in this thread
By the way, some of the people who got burned on J2EE were those developers who were assigned to J2EE projects and couldn't get up to speed in time. So, why are you so angry?
I was wondering when would someone step in with the usual "if you're complaining, you're an incompetent." I must admit though that the phrasing above is very diplomatic, but is in the end the same insult. And still the same old issue of The Emperor's New Clothes. (Surely only idiots can't see the fine clothes our Emperor is wearing.)
But let's not get into that flame-war. Why am I so angry?
Well, want to come deploy this beast on WebSphere 5 for me? The whole application takes 4 hours to export off the test server. The GUI alone takes half an hour to deploy through the Admin Console. (Admittedly, that test system is "only" a two CPU Sun workstation with a gigabyte RAM;)
Anyone from IBM want to exactly explain how does this improve my productivity and reduce the TCO, please? No, I'm serious. I want to know.
Or here's a small sample of other issues, only off the top of my head, which we faced over the last year.
- XA exceptions when using more than one Oracle database in the same transaction? Check. (Fixed in WS 5.0.1.) That caused the whole team to first scramble frantically to diagnose the issue for two weeks... then wait another 42 days for IBM to fix it.
- Severe performance problems in the DataSource when using JAAS? Check. (Fix PQ79683.) More time lost, and more teams from several projects scrambling to find out why that promised land of scalable J2EE architectures... doesn't scale.
- ClassCastExceptions due to an ORB bug on Solaris, when two session beans call each other? Check. More time lost diagnosing IBM bugs, and one huge administrative overhead to keep the application working in the meantime. (Unnamed fix from IBM, which basically made the server crash upon start-up. Obviously never actually tested on WebSphere.)
- Exceptions being silently caught and replaced by other (completely wrong) exceptions? Check. E.g., what should have come as a ClassNotFoundException at deserializing, in WebSphere comes back as a NotSerializableException. Heck, yeah, that's got to improve our speed at diagnosing problems. (Not fixed.)
- Wrong or misleading error messages in the tools? Check. E.g., the Tivoli Perfomance Viewer says that no server has the performance monitoring turned on, instead of saying that the password is wrong. (Not fixed.)
- WebSphere 5.0.2 filling the logs with NumberFormatException lines when performance monitoring was enabled? Check. (Unnamed fix from IBM.)
Etc, etc, etc. Seems to me like WAS 5 alone is enough reason to be angry.
Plus, no, I'm not talking about the excitement of learning new stuff. (Which I do still have.)
I'm talking about the wisdom to sometimes say "ok, this new stuff I've learned might be cool, but here and now it is not what we need." After all, just because you've learned to drive, doesn't mean you should outfit the server with a steering wheel and pedals.
And about the honesty to recommend what the client really _needs_, not the buzzwords you wish to have on your resume. Which is what some of that hype from developpers is all about. As soon as some new buzzword is in vogue, everyone scrambles to get it on their resume. It doesn't matter if the client really needs it, or if it even makes sense for the current problem. All that matters is that at the next job interview you'll have another buzzword to show off.
Which is just as dishonest as if a surgeon deliberately mis-diagnosed you, just so he can get a heart operation on his resume.
