> 3) The docs need to gently coach users that ask "the wrong question"
> because they don't have the proper OO-perspective. eg people who ask
> "how the hell do a SELECT DISTINCT CATEGORY FROM MOVIES ORDER BY ASCENDING
> in the Movies example?" Please pay special attention to newbies with a
> strong relational background 'cause I think most of your converts are
> current webweavers who started with Perl & Msql (or similarly crappy
> tools) and are just getting their first good taste of clean OO in
> WebObjects.
>
> I think all you'd need to do is get 100 new developers and just sit with
> them for a few weeks as they try to figure things out on their own,
> recording their questions...
That's a great suggestion. I think once you become immersed in this stuff
it just makes sense and you forget what its like not understand it.
WebObjects and EOF are an amazing tools once things "click" but if all you
know is how to munge PERL, Java and/or C++ with SQL its not going to make a
lot of sense at first.
Apple should hire a Web company which builds sites with other tools to have
a group of their engineers learn WebObjects and then help Apple fill in the
gaps in the documentation, diagrams, etc. to help them make the transition.
BTW, it would also be nice if Apple would publish UML diagrams for all their
frameworks. It would be nice to have poster-sized versions of these to hang
on the wall.
