NYCPHP Meetup

[Jake McGraw]

On Tue, Jul 28, 2009 at 9:31 AM, Justin Dearing<zippy1981 at gmail.com> wrote:
> If their not using PHPDocumentor, setup a cron job to generate the
> documentation every hour, even if runs locally on your laptop for now. Start
> documenting the code as you make changes.
> Even if there are no javadoc like comments in the code, You'll have a list
> of functions, classes, files, etc.
> Oh yeah, go down to some user group meetings, talk about your experiences at
> your new job. Make sure people don't tell you to run away.
> Regards,
> Justin Dearing
> 2009/7/28 Peter Sawczynec <ps at blu-studio.com>
>>
>> Now what? Guidelines, must-dos, things to avoid, generic new job advice,
>> websites/blogs to review daily, other good advice websites, book(s) to
>> checkout, feedback, thoughts...

Using the vernacular "I have a PHP5 job" is passé. PHP5 is now over
five years old, any PHP job should be a PHP5 job :-P. Couple of
must-dos:

* Use special function "__construct" NOT class name for constructor.
* Use visibility: public, protected, don't just make everything public
* Define the special function "__toString" with something useful,
makes debugging much simpler
* Read, and I mean read, don't skim, through every single page here:
http://php.net/oop

- jake

>>
>>
>>
>> Warmest regards,
>>
>>
>>
>> Peter Sawczynec
>>
>> Technology Dir.
>>
>> blūstudio
>>
>> 941.893.0396
>>
>> ps at blu-studio.com
>>
>> www.blu-studio.com
>>
>>
>>
>>
>>
>> _______________________________________________
>> New York PHP User Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>>
>> http://www.nyphp.org/show_participation.php
>
>
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> http://www.nyphp.org/show_participation.php
>