« Test Driven Patching | Main | Encryption Amendment »

Where's the $$ in Java

Yesterday while browsing around a new weblog I found I came across this statement/question. I must admit I have a similar question. What areas of java pay more or are in more demand? And I wonder that not in the traditional role (architect/VP/Sr Developer/Jr Developer) type thing, but in a specialized knowledge type thing. Crowbar seems to indicate that developers who develop Swing apps are paid less just because of that skill. I certianly hope not since I've been kind of backed into that role through chance, but fortunately the stuff I did is provable magic and not simple VB form builder stuff. Another local guy got loads of contract work just because he let his contract handler know he was playing around with web services. It's not like he only knew how to spell "Whisdel," he actullay had some good knowledge to back it up, but sometimes it makes wonder if Buzzword Bingo is the way to job security. That and the experience we had with some (not all) of the contractors we used to use proved that just because you can monkey around with J2EE middleware doesn't mean you are worth one tenth of the money that is spent on you. So I throw this question out to the blogshpere... Where's the $$ in Java at?

TrackBack

Listed below are links to weblogs that reference Where's the $$ in Java:

» Big bucks from Feelings and Thoughts
Danno wants to earn big bucks ;-) While of course I'm interested in this too, it is in the end [Read More]

Comments (4)

Danno;
Crowbar wants to expound on our statements regarding Swing development. We will make it short and sweet, since as you may know, we are busy rewriting the Air Traffic Control System.
Our observation has been that sub-par server side development is commonly overlooked as it is not immediately evident to the end user. For example, it is a common anti-pattern to load a JDBC driver and make a connection for every request to the server, yet it is quite possible that users may not notice this problem.
On the other hand, a Swing user interface with an equivalent problem would be immediately experienced and in accumulation would make the application unacceptable.
Our point is that the barrier to excelence is much higher developing Swing than it is developing backend services, and consequently, the number of applications based on Swing that are considered crap are higher, per capita (or applica ?) than for panzy Servlet & JSP apps.
Excelent Swing is a rare and precious commodity, and at Crowbar, we wish it was otherwise, but we appreciate it all the same.

I think you're right about web services (which usually means SOAP, UDDI, WSDL), that was my experience during my last round of interviews.

I think J2EE and/or EJB skills will pay you best.

> I think J2EE and/or EJB skills will pay you best.

I can't wait until that's all over. We all see the EJB backlash starting, I just wish it'd play out faster.

Post a comment


About

This page contains a single entry from the blog posted on February 13, 2003 7:59 AM.

The previous post in this blog was Test Driven Patching.

The next post in this blog is Encryption Amendment.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type 3.33