High-hanging fruit
Dec. 26th, 2006 09:54 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
issaferretDecided to take a swing at learning the State of Java Enterprise Software around middle of last week - I had free time, and I wanted to give myself a goal. Being able to program is only sort-of my goal. I don't have the smarts to be an architect, developer, and QA-tester in one body.
My goal has been to familiarize myself with the language at minimum, and learn the scope of the basic technologies. J2EE - now Java 5 EE - is a big damn toolbox, ranging from the Application Servers like Weblogic, Websphere, JBoss, and Glassfish, all the way to management APIs and parsing tools. There's a standard tool for just about everything, and it's _all_ painfully flexible; you have to wade through miles of power to get to simple things.
That's not inherently evil, just painful. I'm stuck with a lot of alphabet soup - JTA, JAXB, JAXM, JAXP, StAX, JMX, JMS, JDBC, EJB, RMI, and so on - that I want to understand enough to be able to know when the person I'm talking to is blowing smoke up my ass, at least... and at best, be able to contribute to the developers more than just the ability to tell them we won't do something.
I'm maintaining a program that surrounds and controls all these things... I wouldn't trust a mechanic who couldn't tell me why not to put diesel in an unleaded-only truck, or one who told me that when my brakes went out, I should just restart the car and hope it works.
Wish me luck... I hope my head doesn't explode.
My goal has been to familiarize myself with the language at minimum, and learn the scope of the basic technologies. J2EE - now Java 5 EE - is a big damn toolbox, ranging from the Application Servers like Weblogic, Websphere, JBoss, and Glassfish, all the way to management APIs and parsing tools. There's a standard tool for just about everything, and it's _all_ painfully flexible; you have to wade through miles of power to get to simple things.
That's not inherently evil, just painful. I'm stuck with a lot of alphabet soup - JTA, JAXB, JAXM, JAXP, StAX, JMX, JMS, JDBC, EJB, RMI, and so on - that I want to understand enough to be able to know when the person I'm talking to is blowing smoke up my ass, at least... and at best, be able to contribute to the developers more than just the ability to tell them we won't do something.
I'm maintaining a program that surrounds and controls all these things... I wouldn't trust a mechanic who couldn't tell me why not to put diesel in an unleaded-only truck, or one who told me that when my brakes went out, I should just restart the car and hope it works.
Wish me luck... I hope my head doesn't explode.
