Comments on: What Makes Good Code?

By: Marty Thornley

Marty Thornley — Fri, 06 Mar 2009 07:55:27 +0000

I have to echo Phil’s comments.

To add to that and answer one of the questions in the article, I definitely prefer to enter and exit php when I need it and go back to html, rather than echo html whenever possible. In a mostly html page at least. When I edit something like functions.php in WordPress, I keep it all php. Seems to make more sense there and functions.php is so quirky it causes less problems.

I think the separation makes it a lot easier to read. I can quickly scan a page and see my layout and easily tell the php statements at a glance, especially in a color-coded html editor.

By: Paul

Paul — Fri, 06 Mar 2009 05:44:57 +0000

My answer is that good code is something that is readable and also the answer of Phil too

By: Phil Palmieri

Phil Palmieri — Fri, 06 Mar 2009 02:58:00 +0000

My answer is that good code is a balance of standards, security and speed of deployment.

When looking at it from the purist end, it should be the least amount of lines you can write to get the job done in the most secure way – with comments of course.

From the business point, good code is standardized, well documents, tested, secure and easily picked up by new developers. – not necessarily the most creative, but the most reliable.

Phil