JEE was not made for the working man.
I mean, if you look at intro docs[0] you are going to see things like custom deployment descriptor capability. In practice what this means is that they expect a deployment person to take an existing working application, in a custom zip file, open the same file that is in charge of the whole container (how it is deployed, how things are named, what classes are and are not loaded) edit incredibly ill-commented xml files, and expect it to work in a new environment straight away.
No. JEE was made by corporations with agendas. BEA, Oracle, IBM etc.. each with their own "value added" piece. Specifications written by corporations are nothing more than joint advertising efforts for their products.
An anonymous grey beard from the early cocaine-80's days of selling computer hardware told me once he went to a demo with a machine the size of a room that only had their tech lead inside with a small system to fake out the real thing. For $3 million dollars they wanted this thing. A guy in a box literally hard-wiring answers.
I spent all week on getting each production version it's own building release branch. I'm still not done.
- It's maven's SNAPSHOT.
- It's svn.
- It's ongoing poor deployment practices.
- It's slow corp machines.
- It's corrupted outlook pst files.
- It's rushed integrations with no real transaction support.
- It's huge static custom css
- It's 100 degree heat walking to and from work
- It's interviews taking 90 minutes.
- It's bamboo's not latest branch version but current repository version.
- It's the COMPLETE LACK OF AUTOMATED TAPE BACKUPS.
- the list goes on and on and on and on
No comments:
Post a Comment