Comments on: Ten PHP Best Practices Tips that will get you a job

By: Tony Parrillo

Tony Parrillo — Thu, 02 Sep 2010 06:04:44 +0000

And Muhkuh, kindly stick to your guns: in one sentence you bash the author for not providing proof of single- vs. double-quoted strings……and then you offer up some B.S. about regexes (which is true, by the way) without offering any sort of benchmarking whatsoever. Hypocrisy stinks.

This is a good, solid list of "don't dos" that will benefit a whole lotta peeps.

By: Tony Parrillo

Tony Parrillo — Thu, 02 Sep 2010 05:56:27 +0000

Friends, I'm choosing to attack the naysayers of the tab movement. It's the absolute, most basic of mathematic principles: four bytes consume more bandwidth than one. So every time you use a space in your rendered code, you're adding a byte to the bandwidth overhead.

So if you have a line of code with six levels of indentation, you're looking at either six bytes (tabs) or twenty-four bytes (spaces…if they're set at four).

We shave single characters in src attributes by renaming 'this-is-the-best-photo.jpg' to 'titbp.jpg'.

While it seems like nitpicking, I just can't abide uninformed commentary.

By: Braeden Petruk

Braeden Petruk — Wed, 11 Aug 2010 20:23:03 +0000

Great article. However, there is an error in your section about loops.

Using count($array) inside a for() statement will actually only execute the count function once, thus rendering a pre-defined variable quite useless.

for() evaluates the three parameters in full before looping through the code between the braces, so it doesn't matter how you pass the data to the construct. You could use return variables from functions for all three parameters without impeding performance.

By: fuxximus

fuxximus — Wed, 04 Aug 2010 02:00:01 +0000

i've read your article, having played around with PHP for the last 5 years, i can't agree with you more, i just think most are gimmicks. I personally pay attention to all of the things you mentioned, and it annoys me to hell when people i work with don't consider as important.

By: muhkuh

muhkuh — Tue, 27 Jul 2010 19:58:26 +0000

Ah the myth about single quotes that are faster than double quotes. Have you profiled the code?

It WAS true with php 3 and early versions of php 4 but please stop to spread these myth!

The article is good but when you say things like "use feature X instead of Y because it is faster!" then please proof it!

Anyway I totaly agree with regex functions versus standard string functions. As long as you don't check the format of an input use standard string functions. And when you want to check the format of input consider the filter functions before you consider regexes!

I agree also to nuno costa. Don't overcomment the code only document the code that needs it (Like a algorithm) and document you classes/functions. But I think thats what you've meant.

By: EllisGL

EllisGL — Tue, 06 Apr 2010 00:45:02 +0000

@Steven I keep seeing code that uses spaces and tabs. *cringes*

By: Steven

Steven — Tue, 06 Apr 2010 00:30:02 +0000

The problem with using tabs instead of spaces is that one developer will use 4 spaces for a tab and another developer will use 3 or 8 spaces. Now no matter what number of spaces you set the tab setting, you cannot get the file to be properly indented.

By: sateeshpatil

sateeshpatil — Mon, 29 Mar 2010 12:29:00 +0000

Good, Need to have such articles ,,,,,,

By: Surendra

Surendra — Fri, 15 Jan 2010 13:13:13 +0000

This is an awesome article and as a programmer i don't find use these small mistakes.

By: 45 Must Read PHP Articles and Resources

45 Must Read PHP Articles and Resources — Fri, 08 Jan 2010 17:44:51 +0000

[...] Ten PHP Best Practices Tips that will get you a job [...]