代码规范

  1. If a class is too big,it should be added comment and have documentation. If the arithmetic is too hard to understand ,i think it should have data flow diagram.(5 points)

    But if the documentation is too simple or no meaning,i don't think it should exist.

    Don't use too many depths if/elseif,divide it and use function.

    Format code before commiting code to cvs.

  2. variable name should be only single meaning .it shouldn't be ambiguity.(5 points)

    Because maintenance time is longer than coding time.

    i think that if the variable name is integer type,it can like this $iName,if variable is string ,it can be $sName,if the variable name is double,it can be $dName,if it is array type,it can be $aName,if it is sql resultset ,it can be $rsName;if it is a tree type,i can be $trName.

  3. Db Function and view Function should be separated.( 3 point)

  4. Try to use exist framework,don't create yourself.(1 point)
          Just Thinking

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值