The Art of Writing Code

When people think of writing code, they often just think of it as writing instructions to perform a certain function. Little care is often given to how the code is presented. You may ask, what’s the point? What’s the difference? After all, the code still runs right? You couldn’t be more wrong…

People who take pride in their work, would love to show it to others. If you cannot even take the slightest effort to make your code presentable to others, it shows that you do not take pride in your work. However, sometimes it is not the coder’s fault. They just don’t know how to write their code properly. Well, it is time to learn

Variable/Function/Class/etc Naming

Descriptive Names

This is by far the most important aspect of writing code. The name should always be able to describe its purpose. Just by reading, a person would know what the variable is for or what the function will do. For example:

Bad:

$var1 = 'Hawk';
$var2 = 'hawk@dannyfoo.com';
$var3 = 'Web Developer';

v( $var2 );

Good:

$name     = 'Hawk';
$email    = 'hawk@dannyfoo.com';
$position = 'Web Developer';

validate_email( $email );

Better:

$staff_name     = 'Hawk';
$staff_email    = 'hawk@dannyfoo.com';
$staff_position = 'Web Developer';

validate_email( $staff_email );

The 3rd example is better because the variable more accurately describes its value. While $name is sufficient in most cases, it can be confusing. Does the e-mail address belong to the staff or the client? Be as descriptive as you can while being concise. Try to keep the names below 32 characters.

Naming Style

If you noticed, in my examples i used an underscore to seperate the words. This is purely personal preference, i just find it easier for me to read. You may choose to use another common method like staffName, staffEmail, staffPosition, validateEmail(). You will normally see this used in most Microsoft based applications.

Also, try not to abbreviate too much. If you have to shorten the names, use well-known abbreviations like number being shortened to no. or num.

Code layout

1 instruction per line

We have plenty of lines to use, it is not in short supply. So use them to aid readability.

Bad:

$staff_name = 'Hawk'; $staff_email = 'hawk@dannyfoo.com';
$staff_position = 'Web Developer'; validate_email( $staff_email );

Good:

$staff_name     = 'Hawk';
$staff_email    = 'hawk@dannyfoo.com'
$staff_position = 'Web Developer';

validate_email( $staff_email );

I think its pretty clear which is easier on the eyes

Whitespaces are your friends

How would you like it if you had to read an article that did not use any whitespaces to seperate words? For example: (Howwould youlikeitifyouhadtoreadanarticlethatdidnotuseanywhitespacestoseperatewords?). See, even one sentence is going to make your eyes bleed! Code should be treated the same way.

Bad:

$staff_name='Hawk';
$staff_email='hawk@dannyfoo.com'
$staff_position='Web Developer';

validate_email($staff_email);

Good:

$staff_name = 'Hawk';
$staff_email = 'hawk@dannyfoo.com'
$staff_position = 'Web Developer';

validate_email( $staff_email );

Better:

$staff_name     = 'Hawk';
$staff_email    = 'hawk@dannyfoo.com'
$staff_position = 'Web Developer';

validate_email( $staff_email );

Lining up the values like the 3rd example makes it alot easier to read. It may not seem like much when you have a few variables like this, but when it gets longer you’ll find out just how much easier it is. Heck, if that doesn’t persuade you… it is neat! That should be a good enough reason :p

Indentation

Open any technical book, take a look at its table of contents. You will see the main chapters and sub-chapters. The sub-chapters are always indented to clearly show that these chapters are part of main chapter. The structure of the chapter is clear, your code should also be the same. At one glance, your structure should be clear.

Bad:

while ( $condition = true )
{
dosomething();
if ( $condition = false )
{
break;
}
}

Good:

while ( $condition = true )
{
	dosomething();
	if ( $condition = false )
	{
		break;
	}
}

See how the indentation makes things so much clearer? This doesn’t just apply to programming, when you do your HTML you should also always indent your code properly to give it a clear structure. Once again short examples may not show much benefit. I do not want to make this blog entry too long so i didn’t include larger chunks of code.

Real Example

Now that we have learnt the basics of writing readable code, lets take a look at a real example and how we can improve it to make it better. Lets take a look at a code snippet to create a JPEG thumbnail from a JPEG file if the JPEG image exceeds a certain width.

$width=425;
$quality=80;
$dimension=getimagesize($image_file);
$pic_width=$dimension[0];
$pic_height=$dimension[1];
$src=imagecreatefromjpeg($image_file);
if ($dimension[0]>$width){
$height_ratio=($pic_height/$pic_width);
$resized_width=$width;
$resized_height=$width*$height_ratio;
}else{
$resized_width=$pic_width;
$resized_height=$pic_height;
}
$resized=@imagecreatetruecolor($resized_width,$resized_height);
@imagecopyresampled($resized,$src,0,0,0,0,$resized_width, $resized_height,$pic_width,$pic_height);
imagejpeg($resized,$picture_path.$image_name,$quality);

As you can see, its pretty ugly and hard to read. No whitespaces, poor variable naming and little use of new lines. Lets make this better.

$thumbnail_width = 425;
$jpeg_quality    = 80;

$dimension  = getimagesize($image_file);
$pic_width  = $dimension[0];
$pic_height = $dimension[1];

$source = imagecreatefromjpeg($image_file);
if ( $dimension[0] > $width )
{
    $height_ratio   = ( $pic_height / $pic_width );
    $resized_width  = $thumbnail_width;
    $resized_height = $thumbnail_width * $height_ratio;
}
else
{
    $resized_width  = $pic_width;
    $resized_height = $pic_height;
}
$thumbnail = @imagecreatetruecolor( $resized_width,
                                    $resized_height );

@imagecopyresampled( $thumbnail, $source, 0, 0, 0, 0,
                     $resized_width, $resized_height,
                     $pic_width, $pic_height );

imagejpeg( $thumbnail, $picture_path . $image_name,
           $jpeg_quality);

There much easier to read now isn’t it? There are many ways to make code readable, each person will have their own preference. Just make sure whatever that preference is, you stick to it. If in a team, ensure that everyone agrees to a coding standard. That way the code wouldn’t look like rojak :p. Above all, be consistent.

Since this entry is called “The art of Writing Code”, I’ll add a link to ASCII art code. The code is written and formatted to create an image and it is fully functional. Of course i do not recommend anyone to do this for serious projects, but for entertainment sake it could be fun . See some code art!

Comments

Have something to say? Leave a comment