Tag Archives: best practices

Attract web traffic with images – 2 Important Points to Remember

Posted by on August 23, 2012 No comments

How to attract web traffic with images?

Many bloggers, Website owners neglect this valuable source of search engine traffic through images used in their blog or pages in the website.

The most important thing to know is that while people can see our website images,
but not the search engines because they simply cannot read the images. Search engines only read the words in the tags and titles we give in our images.

Two very important points to remember when adding images to the web page:

  1. All images must have ALT and TITLE attributes defined. This is basically the image equivalent of the doc title or meta description for the web page.
  2. We should name the Images with a relevant name.

For example 

<img src="tv.gif" alt="Wide Screen Television" title="On Sale Now 50% OFF!" />

Have you found this information is useful? Provide feed,comments or suggestions below

Share|

Smell my Code. Code smell ? What’s code smell?

Posted by on February 17, 2012 No comments

Code smell is any symptom in the source code of a program that possibly indicates a deeper problem. It is the process of identifying bad software program and altering in such a way that it does not alter the external behavior of the code, yet improves its internal structure. Code smell can even take a bad design and rework it into a good one.

Some common Coding smells:

  1. Duplicated code: identical or very similar code exists in more than one location.Long method: a method, function, or procedure that has grown too large.
  2. Large class: a class that has grown too large. See God object.
  3. Too many parameters: a long list of parameters in a procedure or function make readability and code quality worse.
  4. Feature envy: a class that uses methods of another class excessively.
  5. Inappropriate intimacy: a class that has dependencies on implementation details of another cclass.
  6. Lazy class / Freeloader: a class that does too little.
  7. Contrived complexity: forced usage of overly complicated design patterns where simpler design would suffice.
  8. Excessive use of literals: these should be coded as named constants, to improve readability and to avoid programming errors. Additionally, literals can and should be externalized into resource files/scripts where possible, to facilitate localization of software if it is intended to be deployed in different regions.
  9. Ubercallback: a callback that is trying to do everything

Determining what is and is not a code smell is often a subjective judgment, and will often vary by language, developer and development methodology.

There are some tools such as Checkstyle, PMD and FindBugs for Java, to automatically check for certain kinds of code smells.

 

Share|