Keep it clean, and keep it simple--that is the maxim software developers should adhere to.

1. Understand the problem

   For instance, Lee said, there are different algorithms engineers can use to write a sorting program.

   To select the right one to use, developers need to first understand the size of the data–that the sorting program will be administered on–in order to decide which is the right algorithm to use. "Choosing the wrong one would put your application in jeopardy in future," he said.

2. Use appropriate tools

   Quoting American psychologist Abraham Maslow, Lee read: "If the only tool you have is a hammer, you will see every problem as a nail."

   This Maslow concept has become so popular among software developers that it has been dubbed the "Golden Hammer" rule, which cautions engineers with limited knowledge or training of solutions that they run the risk of using only tools they are familiar with, but that may not be the most appropriate, when they develop a new program.

3. Strive for simplicity

   Programmers should develop applications that are:

   • Easy to understand;
   • Easy to explain;
   • Easy to maintain;
   • and Easy to document.

4. Keep your code clear

   Lee said: "Put yourself as an author, how would you write something that others can easily understand and follow your thoughts? That’s how a programmer should code as well."

5. Learn to debug

   "Sometimes, there are bugs in your codes, or in other [software] libraries that you may have bought or downloaded that you cannot control," Lee said, underscoring the need for developers to "test early, test often".

6. Leverage what is available

   Developers should also look for solutions or algorithms that are already publicly available, such as those highlighted in developer forums and mailing lists.

7. Continue to learn

   Can developers then balance the commercial need to push out applications as quickly as possible, with the need to write codes that are clean?

   Lee believes they can. "A lot of people say if they don’t have quantity time, at least they have quality. That’s not true… You can’t have quality time if you don’t put in quantity time," he said. "There’s commercialization [in software development] but there’s also ‘art’ and ‘good’ codes. And you can achieve both."