NYCPHP Meetup

NYPHP.org

[nycphp-talk] IT Policies

Jonathan Face jface at mercenarylabs.com
Thu Oct 19 15:50:03 EDT 2006


In this vein, determine a standard syntax for variable naming.

IE, $this_variable versus $thisVariable.

Less confusing that way.

Ben Sgro (sk) wrote:

>I think code reviews are great, they give people a change to highlight well 
>done code and
>point out errors and common pitfalls.
>
>Plus people can't sneak kludges in as easily.
>
>Having a document that states comment style, code style etc can help as 
>well.
>At my previous job it was required all new highers read the doc.
>Having code reviews made sure the guidelines laid out in the doc where 
>followed.
>
>As you stated, speaking to the other developers to find out what the 
>standards will be is the best idea,
>they hopefully you can avoid disagreements with what style will be 
>used..since those involved will be
>able to voice their opinions.
>
>Less cooks is better, unless it means people are waiting to check stuff in 
>on live.
>If they have a development server that mimics live then its not really a 
>problem,
>they can test and feel pretty condfident about their code before they check 
>it in.
>
>If you dont have a development server that mimics the live server, I would 
>get one ASAP.
>
>good luck!
>
>- Ben
>----- Original Message ----- 
>From: "Brian Dailey" <support at dailytechnology.net>
>To: <talk at lists.nyphp.org>
>Sent: Thursday, October 19, 2006 3:27 PM
>Subject: [nycphp-talk] IT Policies
>
>
>Another "Ask the NYC PHP Crowd" question...
>
>I've been given the responsibility of developing a policy for a small
>(and growing) team of developers. By "policy" I mean defining how
>"development" code becomes "live" code. The point is to minimize
>problems in the program itself and the database behind it.
>
>How do you balance flexibility with minimizing risk? I've talked to a
>few of my fellow developers, and a few of them have talked about the
>usefulness of code review. That seems to be good idea, as does
>allowing only or two people to place development code on the live side
>(less cooks in the kitchen).
>
>Any suggestions on stuff I should think about?
>
>- Brian
>_______________________________________________
>New York PHP Community Talk Mailing List
>http://lists.nyphp.org/mailman/listinfo/talk
>
>NYPHPCon 2006 Presentations Online
>http://www.nyphpcon.com
>
>Show Your Participation in New York PHP
>http://www.nyphp.org/show_participation.php
>
>
>_______________________________________________
>New York PHP Community Talk Mailing List
>http://lists.nyphp.org/mailman/listinfo/talk
>
>NYPHPCon 2006 Presentations Online
>http://www.nyphpcon.com
>
>Show Your Participation in New York PHP
>http://www.nyphp.org/show_participation.php
>  
>




More information about the talk mailing list