Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!not-for-mail
From: "M. Strobel" <sorry_no_mail_here@nowhere.dee>
Newsgroups: comp.lang.php
Subject: Re: Books?
Date: Tue, 20 Mar 2012 10:19:53 +0100
Lines: 33
Message-ID: <9sr0dpFon8U1@mid.uni-berlin.de>
References: <8sGdneILNJwueP3SnZ2dnUVZ_v2dnZ2d@giganews.com> <7257183.754.1332178327363.JavaMail.geo-discussion-forums@vbhv6> <YsmdnbjWNvCPffrSnZ2dnUVZ_gidnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: news.uni-berlin.de GoPjvYpXNJ5NXgxA1NtRrQ9o/ccmTs/K3NihibFI4mQ86fIWw=
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.27) Gecko/20120215 Thunderbird/3.1.19
In-Reply-To: <YsmdnbjWNvCPffrSnZ2dnUVZ_gidnZ2d@giganews.com>
Xref: csiph.com comp.lang.php:5188

Am 20.03.2012 02:39, schrieb Christopher M.:
> "macca" <ptmcnally@googlemail.com> wrote in message 
> news:7257183.754.1332178327363.JavaMail.geo-discussion-forums@vbhv6...
>> PHP 5 Objects, Patterns, and Practice
>> Matt Zandstra
> 
-- cut ...
>  and learn about PHP best coding practices.

- use proper code indenting to make your code readable
- document your code with phpDocumentor or other
- use meaningful variable and function names
- use an editor with syntax highlighting to help find any unbalanced quotes
  and parentheses before running the script
- if something does not work like expected: use a debugger to inspect your
  variables at every execution step, IMO a must for serious programming
- get used to a version control system early, you will populate your file system
  with test1.php, test2-old.php, test2-1.php and so on not knowing what you will need
  later and what to delete

This was the easy advice, now the difficult:

- break down a problem into smaller 'working units' using functions and objects
- design your functions (and methods) to work on data passed in by parameters, the
  benefits will be better isolated testing, and reuse of code
- test your code after every logic step
- work on your understanding of the whole system: client browser, IP (address, ...),
  TCP (port, SSL, ...), DNS, HTTP (headers, ...), HTML, CSS, JavaScript, web server
  settings, PHP settings, logging, ...

There is a reason why good programmers can ask for high hourly rates.

/Str.