Re: Getting Started - Xcode or ?
Re: Getting Started - Xcode or ?
- Subject: Re: Getting Started - Xcode or ?
- From: Chuck Hill <email@hidden>
- Date: Fri, 6 Oct 2006 10:49:57 -0700
Hi Seth,
On Oct 5, 2006, at 9:22 PM, Seth Norris wrote:
I have just applied for a position that requires a
"commitment to learning WebObjects"
I would interpret that as "The last people we hired spent all their
time bitching about using WebObjects and how we should be using
Struts and Hibernate and how this was no good for their resumes. If
you are one of those people, don't apply." :-)
That said, enthusiasm is always appreciated.
I am excited about this, but am not sure
where to start. I have been reading through all the
documentation from Apple, but am getting somewhat
bogged down.
Yes, the learning curve is like the side of a cliff.
I am hoping to have at least gotten my
hands dirty before the interview.
I would worry less about the tools and running code and more about
getting the Big Picture. That is more likely to impress (or would
impress me more).
I have been trying
to use XCode and have been messing around with
EOModeler. It seems very cool, but I have not gotten
very far. I have been looking online for other
resources/tutorials but the pickings seem slim. Any
suggestions? Am I wasting my time with XCode?
You might find them easier to use out of the box than Eclipse and
WOLips. For the short term (until the interview), I would stick with
Xcode. That is not advice you will see me give often on this list!
Is
there a book I should get? Last but not least: If you
were interviewing someone for a position that would
require them to use WebObjects, what would you like to
see from them, knowing that they have no previous
experience?
I don't think I have ever interviewed anyone _with_ WebObjects
experience! The first thing I look for is a very good grasp of OO.
Not the text book stuff you read in school, but the ability to
actually explain it and why the elements are of value in software
development. Next, do they know any common patterns (singleton,
observer, MVC) and can they explain how they work and why that is of
value. What I am looking for is someone who learns to the point of
actually understanding rather than parroting back parts of a book.
If you can learn, I can teach you the rest. I don't worry much about
HTML or CSS, if you can learn WO you can easily pick that up. I
like to see a good knowledge of basic SQL and indexes. Other things
I try to ferret out is attitude toward testing, documentation,
commenting, schedule pressure and (probably most important) team
work. If you can't get along well on a team, I don't want you
around. At all.
If you have any knowledge of ORM (Object Relational Mapping) that
would be a big plus. Extra bonus points for knowing Hibernate,
TopLink, Castor, ActiveRecord, JDO or any other (not quite up to EOF
standards) variant. A working knowledge of multiple languages (e.g.
Java, SmallTalk, and Lisp) is impressive.
The fact that you have actually gone and started to read the
documentation is amazing. Again, I would still to the docs and not
bother with coding. The big picture is what you need to start with
and will have the most talking value in an interview. Focus on EOF,
less so on the less complex WebObjects (templating) side.
I would focus on understanding what is in these:
http://developer.apple.com/documentation/WebObjects/
WebObjects_Overview/index.html
http://developer.apple.com/documentation/WebObjects/
Enterprise_Objects/index.html
http://developer.apple.com/documentation/WebObjects/
Enterprise_Objects/index.html
If you read those before the interview, could talk intelligently
about some of it and ask intelligent questions about the rest, I
would hire you (providing you had all the other basics).
Best,
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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