If you look at salaries

Post #125,772 by tuberculosis 11/14/03 10:18:23 PM 8/21/07 12:46:45 PM Reply	If you look at salaries the J2EE developers/architects are pulling down 10-30% more cash than say people who do kernel hacking or device drivers. To me that seems wrong as the latter definitely requires more skill. OTOH, 75% of J2EE development has nothing to do with writing code - its fucking bookkeeping - which is what makes it such a drag. What I find interesting is that the leading app server vendor is willing to come out and say that its too complicated. You'd think they'd be more interested in maintaining the status quo. So I find the honesty refreshing. "I believe that many of the systems we build today in Java would be better built in Smalltalk and Gemstone." -- Martin Fowler, JAOO 2003 Edited by tuberculosis Aug. 21, 2007, 12:46:45 PM EDT If you look at salaries the J2EE developers/architects are pulling down 10-30% more cash than say people who do kernel hacking or device drivers. To me that seems wrong as the latter definitely requires more skill. OTOH, 75% of J2EE development has nothing to do with writing code - its fucking bookkeeping - which is what makes it such a drag. What I find interesting is that the leading app server vendor is willing to come out and say that its too complicated. You'd think they'd be more interested in maintaining the status quo. So I find the honesty refreshing. "I believe that many of the systems we build today in Java would be better built in Smalltalk and Gemstone." -- Martin Fowler, JAOO 2003 Collapse All History
Post #125,785 by FuManChu 11/15/03 12:09:47 AM Reply	Since when does more skill == more profit?
Post #125,786 by admin 11/15/03 12:49:03 AM Reply	Depends on your outlook... Making the beast perform does require a certain amount of skill. :-P Of course, if you don't use EJB, a lot of the bookkeeping goes away. BTW, good call on the Rod Johnson book. I'm digging it. He has a lot of good bad things to say about J2EE. I'm looking into his [link\|http://www.springframework.org/\|Spring Framework], as well -- it's become a full-fledged open source project. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #125,788 by deSitter 11/15/03 1:10:28 AM Reply	Mission statement J 2EE should be easier to use It's best to program to interfaces, rather than classes. Spring reduces the complexity cost of using interfaces to zero. JavaBeans offer a great way of configuring applications. OO design is more important than any implementation technology, such as J2EE. Checked exceptions are overused in Java. A framework shouldn't force you to catch exceptions you're unlikely to be able to recover from. For non-experts, could you elaborate on this, based on your experience? -drl
Post #125,935 by broomberg 11/16/03 8:05:59 PM Reply	Supply and demand Not a big call for deice driver writers or kernel hackers.
Post #126,024 by ben_tilly 11/17/03 10:36:14 AM Reply	Plus the relative supply is greater Kernel hacking is more fun than J2EE. Cheers, Ben "good ideas and bad code build communities, the other three combinations do not" - [link\|http://archives.real-time.com/pipermail/cocoon-devel/2000-October/003023.html\|Stefano Mazzocchi]
Post #126,118 by tuberculosis 11/17/03 4:07:01 PM Reply	Ain't that the truth (more fun). "I believe that many of the systems we build today in Java would be better built in Smalltalk and Gemstone." -- Martin Fowler, JAOO 2003

Welcome to IWETHEY!