Boy, am I glad to see someone say that the sf documentation needs
examples and more cross-references to tutorials and other places where
elements can be seen in practice. I'ts all well and good for the
senior developers to sit back on their heals and smugly say, "Well, if
you were a REAL developer, you would know that," but the simple truth
is that everyone goes through a learning curve both as developers and
as sf developers. Putting stuff in the docs that is useful to the
less-experienced isn't a waste of time. It just helps those that like
what they see but struggle to get going with it become experienced,
productive developers. We're not all journeymen. Thats not a bad
thing, its just reality. If you want the system to be successful -
i.e., adopted and widely used - then you'll realize that part of the
process is to bring the newbies along rather than kicking them in the
teeth at every opportunity just because it makes you feel superior to
do so.
On Sep 18, 8:29 am, david <da...@inspiredthinking.co.uk> wrote:
{snip}
>
> The API documentation of SF should be linked back to the tutorials -
> giving examples of usage and allowing people to refer to examples.
>
{snip}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
