That's it, I want a divorce

Question

Hi ppl,
Last Thursday I reached a conclusion. J2EE is too big, too complex, too picky for one person to understand on their own.
I think maybe J2EE is developed by teams of specialists. I'm trying to implement the whole thing.
I think maybe J2EE is developed by teams with powerful tools. I'm trying to use Sun's basic tools, the
deploytool, CloudScape.
So I met my client today, gave them a hefty credit note, and I've started re-writing in PHP.
I feel free. One line of PHP replaces three of J2EE. I know what PHP does. I can use myAdmin to interrogate my database to check what's worked. I know SQL. I achieved in four hours on Sunday what would have taken me more than a week in J2EE.
Maybe if I'd pressed on I could have beated it. But the signs weren't good. A couple of years ago I got a first class honours degree. We studied Java and J2EE. Despite that, it beat me.
So thanks for all your help, especially you Annie, but if a shadow passes over your desks tomorrow it'll be me dancing into the PHP sun.
Gnight all.
J

Answer 1

Last Thursday I reached a conclusion. J2EE is too
big, too complex, too picky for one person to
understand on their own.
huh What was that? I manage to develop medium sized applications all by myself. Of course, I give realistic deadlines for that.
I think maybe J2EE is developed by teams of
specialists. I'm trying to implement the whole
thing.Mostly yes.
I think maybe J2EE is developed by teams with
powerful tools. I'm trying to use Sun's basic tools,
the
deploytool, CloudScape.That's where something goes wrong. You depend on tools and things start going haywire.
So I met my client today, gave them a hefty credit
note, and I've started re-writing in PHP.
I feel free. One line of PHP replaces three of J2EE.
I know what PHP does. I can use myAdmin to
interrogate my database to check what's worked. I
know SQL. I achieved in four hours on Sunday what
would have taken me more than a week in J2EE.Yeah, PHP has some advantages. But in my case, I'd rather code an application in J2EE and that would be much faster than PHP. The trick is to have some reusable code. :P
Maybe if I'd pressed on I could have beated it. But
the signs weren't good. A couple of years ago I got a
first class honours degree. We studied Java and J2EE.
Despite that, it beat me.I never managed to flunk an exam yet. But I'm still not good at cryptography after numerous attempts to master it, for the past two years. :( That doesn't dishearten me.
So thanks for all your help, especially you Annie,
but if a shadow passes over your desks tomorrow it'll
be me dancing into the PHP sun.I might dance when I find security holes in that sun. Be careful, anyway! It might get too hot in the Sun. ;)
Best wishes,
Athena.