RE: [PHP] tutorial ideas
| From: | Mark Peoples | Date: | Thu, 12 Oct 2000 00:30:43 +0000 |
| Subject: | RE: [PHP] tutorial ideas | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-19732@lists.php.net to get a copy of this message | ||
What I think would be nice would be some sort of algorithm 'hangout' or
whatever, like, algorithmshed.com <g>
Sometimes grasping a concept is better than understanding the code. When you
know *how* something works, you get the concept behind it and learn it's
strengths and weaknesses and know how you can write efficient code. It's
usually just a matter of time before you can implement it.
In other words, if I took an airplane's engine apart, I'd want to know how
it works before I actually worked (destroyed <g>) it.
Speaking of algorithms...has anyone tackled the shortest path using distinct
points yet? =)
marco
-----Original Message-----
From: Jeff Lacy [mailto:jeffdl@mn.mediaone.net]
Sent: Wednesday, October 11, 2000 5:23 PM
To: php-general@lists.php.net
Subject: Re: [PHP] tutorial ideas
Sometimes, I agree with you, Justin. I believe that usually, tutorials are
better than script galleries. Script galleries are often just the script
itself. Tutorials can be fairly bad too. Bill, you should have both really
well documented examples and tutorials. Either one by itself is incomplete.
I don't completely agree with Justin because tutorials can discourage
creativity. You see how to do it one way and then you never try to do it
another. In an example, you have to really try to understand it and then
when you do understand it, you understand all of the parts. Then you will
be more creative, which is what you want, I think.
Please, no flames. Just my $0.025.
Jeff
"Justin French" <justin@indent.com.au> wrote in message
news:39E41E8B.2D4CB5DE@indent.com.au...
> Bill Zeller wrote:
>
> > If anyone has any ideas or has a problem they can't
> > solve, please feel free to email me.
>
> Specific problems *may* provide you with some nice
> content, but I believe that generalised, but IN DEPTH
> tutorials are what is needed.
>
> Realy no need to preach your philosophy or anything
> like that (i've seen too much of that), but I believe
> well structured, in depth tutorials on some of the
> curly topics will provide a strong user base hanging
> on your every word... rather than providing a one-off
> sample, I think tutorials need to be about teaching
> the person to stick up for themselves -- write their
> own regular expressions, validate their own unique
> forms, deal with their own file systems, manage their
> own data, build their own do-hickeys, rather than
> seeing a simple sample that skims the surface.
>
> On a side topic, the PHP manual is very thin -- it
> make makes a lot of assumptions about the programmer's
> general knowledge, a set of REALY basic tools (error
> handling, 'or die', etc etc come to mind) that turn
> home-made php messes into real-world solutions would
> be outstanding!!
>
>
> Justin French
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
> For additional commands, e-mail: php-general-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net
For additional commands, e-mail: php-general-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net