Re: Learning Curve
Re: Learning Curve
- Subject: Re: Learning Curve
- From: Sean Warburton <email@hidden>
- Date: Wed, 12 Jan 2005 23:48:27 +0000
Thanks Guido,
I think its' easy to fall into the trap of listening to people like
Chuck sing the praises of WO and how easy it is to use when compared to
other frameworks and then mistakenly take the word easy out of context.
It's obviously a very complex product and I'm glad I asked the question
now, I'm sure the advice I've been given by everyone will have saved me
a lot of problems down the line.
The job isn't a critical one, it's for a friends car parts business and
it's more speculative than mission critical, so no harm would have been
done in the long run, he just wouldn't have paid me ;-)
On 12 Jan 2005, at 23:38, Guido Neitzer wrote:
"Sean Warburton" <email@hidden> wrote:
Thanks Chuck, Fabian & Art,
You're all telling me what I really knew in my heart of hearts, I
probably just needed to hear it straight from the horses mouth. I
suppose I better get my head into the books again. I appreciate you
taking the time to offer the advice, keep an eye out for me in the
future, I'll be back to badger you all.
I can tell by my own experience, that you must must must be
comfortable with
standard object orientated development (not neccessarily in Java).
Also you
will fight against tons of material.
See this:
- You need to learn to use very complex development environment (Xcode
or
Eclipse - Xcode is easier, Eclipse more powerful).
- You need to think "object orientated".
- You need to learn at least some basic principals of Java.
- You need to get comfortable with WebObjects.
I'm currently developing my first large application with WebObjects,
I'm not
an experienced developer and it is a very frustrating experience. It's
slow.
I'm fighting against Eclipse, CVS, WOLips, Project Wonder, Validation,
complex database design, and all the other problems ...
If you only have 20 weeks and a mission critical application: Don't do
it.
It would be learning WebObjects the hard way - like I do. 18 hours a
day a
normal business currently. I would be three times faster with a less
complex
tool, but the portal will be a large one and currently I'm the only
developer, so I need a robust tool and community behind it.
If you start using WebObjects, don't use complex toolkits like Eclipse
(do
this only, if you are on Windows), don't use Wonder, and plan your
budget
with about 25% percent for external professionals. Than you are on a
good
way.
A client of mine has asked me to quote for a small and relatively
simple
e-commerce site and I'm faced with a dilemma.
If it is really simple, perhaps it can be done if you are comfortable
with
object orientated development, a little bit of Java and a bunch of
optimism.
If not, use another tool or let others do the job (perhaps you know
WebObjects developers and you can build a team).
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden