Comments on: Clean and efficient coding technique in PHP http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html Useful Tutorials, Scripts , Tips, and Resources for all PHP and Ajax beginners and experts . Mon, 07 May 2012 21:11:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: meridia http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-5603 meridia Thu, 19 Aug 2010 12:28:03 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-5603 nice articvle nice articvle

]]> By: ????? ?????? ????? - ::IDMania FORUM:: http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-4866 ????? ?????? ????? - ::IDMania FORUM:: Wed, 02 Dec 2009 23:34:42 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-4866 [...] [...] [...] [...]

]]> By: Sam IT http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-4606 Sam IT Tue, 22 Sep 2009 02:09:40 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-4606 Agreed with pretty much everything but just wanted to add that in many cases I use classes instead of functions so the code is better organized and clearer. For example instead of calling a function such as: get_customers_profile(); I would use: $customer->get_profile(); Or if I use a framework (I usually do) such as Codeigniter: $this->customer->get or get_profile. Much easier to keep the code clean and organized when it's in classes (same idea with folders). Nice blog, keep it coming! :-) Agreed with pretty much everything but just wanted to add that in many cases I use classes instead of functions so the code is better organized and clearer.

For example instead of calling a function such as:

get_customers_profile();

I would use:

$customer->get_profile();

Or if I use a framework (I usually do) such as Codeigniter:

$this->customer->get or get_profile.

Much easier to keep the code clean and organized when it’s in classes (same idea with folders).

Nice blog, keep it coming! :-)

]]> By: pusp jodhi http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-4243 pusp jodhi Thu, 23 Jul 2009 13:02:42 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-4243 i want to learn the standerd coding style in php. please if it can be possible please forward me i want to learn the standerd coding style in php. please if it can be possible please forward me

]]> By: Ellis Geeklab.net http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-25 Ellis Geeklab.net Sat, 22 Dec 2007 23:34:00 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-25 For the switch() - the code is a lot easier to read in my opinion. But I have seen bench marks showing that switch is slightly slower and vice versa. For the switch() – the code is a lot easier to read in my opinion. But I have seen bench marks showing that switch is slightly slower and vice versa.

]]> By: Michael http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-24 Michael Sat, 22 Dec 2007 16:23:00 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-24 I would rather bug the ppl writing the interpreter then take the effort to bring the 'best practice' of rewriting switch to if else statements. <br/><br/>As noted above: write it cleanly and then profile and then take action accordingly. Practice also shows that when profiling the 'hotspots' or bottlenecks are usually not in the place one expects. In short don't micro-optimize things.<br/><br/>"Commenting code line by line (or as near to line by line as is needed to clearly explain what operations are being performed)." I can't disagree more. comment blocks of code; this way it ensures that your code is organised. This is because it forces the programmer to make one block of code do one thing(and do it well) and thus leave your code untangled. And as you don't comment lines it creates a limit to the amount of things that one line of code does. This removes (old) C++ alike-style line of code where a shitload of operations is done and everyone has to look (adleast) twice(including the one who wrote the line) to figure out what's going on. <br/><br/>"Making code as modular and reusable as possible."<br/><br/>Is dangerous to say too; you can go overboard. Tbh I would go with something along the same lines as profiling. See that it repeats itself first and then refactor it out. Now I know PHP-refactoring support is limited at this time but I'm sure it's there 'tomorro'. I would rather bug the ppl writing the interpreter then take the effort to bring the ‘best practice’ of rewriting switch to if else statements.

As noted above: write it cleanly and then profile and then take action accordingly. Practice also shows that when profiling the ‘hotspots’ or bottlenecks are usually not in the place one expects. In short don’t micro-optimize things.

“Commenting code line by line (or as near to line by line as is needed to clearly explain what operations are being performed).” I can’t disagree more. comment blocks of code; this way it ensures that your code is organised. This is because it forces the programmer to make one block of code do one thing(and do it well) and thus leave your code untangled. And as you don’t comment lines it creates a limit to the amount of things that one line of code does. This removes (old) C++ alike-style line of code where a shitload of operations is done and everyone has to look (adleast) twice(including the one who wrote the line) to figure out what’s going on.

“Making code as modular and reusable as possible.”

Is dangerous to say too; you can go overboard. Tbh I would go with something along the same lines as profiling. See that it repeats itself first and then refactor it out. Now I know PHP-refactoring support is limited at this time but I’m sure it’s there ‘tomorro’.

]]> By: Topbit http://roshanbh.com.np/2007/12/clean-and-efficient-coding-technique-in-php.html/comment-page-1#comment-23 Topbit Sat, 22 Dec 2007 12:11:00 +0000 http://roshanbh.com.np/clean-and-efficient-coding-technique-in-php/#comment-23 echo 'Name :', $name, '. Address : ', $add, '. Email ', $email, '.';<br/>// no concatenation involved<br/><br/>I wouldn't bother rewriting it though if I had originally written it another way - chances are the time spent editing it would be more than the time a CPU takes to run it 10,000 times. CPUs are cheap - I am not.<br/><br/>Such nano-optimisations are inevitably blown away by several orders of magnitude with poor algorithm choices, database or file-system accesses (unless they are perfectly optimised - which isn't going to happen anyway) or just using a library or framework that takes more time than it could, but you use it because it will save you a few minutes (or hours, or days) development.<br/><br/>As always, write clean, secure, and easy to maintain code first. Then, and only <em>if</em> it is not fast enough, look for the best thing to optimise - and just do that. Rinse, and repeat, if required. echo ‘Name :’, $name, ‘. Address : ‘, $add, ‘. Email ‘, $email, ‘.’;
// no concatenation involved

I wouldn’t bother rewriting it though if I had originally written it another way – chances are the time spent editing it would be more than the time a CPU takes to run it 10,000 times. CPUs are cheap – I am not.

Such nano-optimisations are inevitably blown away by several orders of magnitude with poor algorithm choices, database or file-system accesses (unless they are perfectly optimised – which isn’t going to happen anyway) or just using a library or framework that takes more time than it could, but you use it because it will save you a few minutes (or hours, or days) development.

As always, write clean, secure, and easy to maintain code first. Then, and only if it is not fast enough, look for the best thing to optimise – and just do that. Rinse, and repeat, if required.

]]>