I would not call them "template engineers", but I already called them
scripters.
Anyway, I am sure there is an intermediate class of coders and there
are much more of them (with different degrees of skill) than of the
so called "Java engineers".
My experience is that they are able to take over after I build a basic
template by placing the necessary markers/instructions on the basic
HTML. Being used to do tasks like writing/changing simple Javascript,
they have no problems understanding the very basic syntax of these
"template languages".
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: Geoff Soutter [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 15, 2001 02:35
>
> Seems to me that your argument rests on the assumption that there exists
> such a beast as a "template engineer" - someone who is skilled in HTML and
> who understands coding without ever having had formal programming
> training.
> Call me traditionalist, but having coding done by non-coders is a
> recipe for
> disaster. For example, I think that a template engineer who was capable of
> rewriting templates to split a form across several pages would probably be
> worth paying as much as a Java coder anyway. For example, you can easily
> hire a qualified HTML coder or a Java coder, but it's pretty difficult to
> hire a qualified "template author", especially when you want them to know
> your own flavour of YATL.
>
> Saying all that I'm sure if you set up your organisation with these three
> classes of developers it would work. It's simply a question of which way
> would be more efficient overall. I favour the 2 role way, you the 3 role
> way.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
