To employees, salary is very important. To employers, paying salary is a crucial responsibility. Once issues about salary occur between employees and employers, the employer will be put into a difficult position. Not only will the employer be facing law risk, the employer will also be facing a bad impact on its fame.
How to design a motivating payment system is one of the most important tasks for the employers to think about.

The blogosphere was flooded with sarcastic comments when Microsoft announced the future Windows Azure Platform Applicance offering at WPC earlier this month, quickly dubbed “Azure-in-a-Box”. eBay and large datacenters will implement Windows Azure cloud infrastructures in large server centers, supported by HP, Dell and Fujitsu.  But cloud in a box sounds like a contradiction, right? Cloud computing was supposed to provide endless scale and elasticity, how could you get this if confined to a single container? 

 I think the more dogmatic cloud prophets are missing the larger point. Yes, global clouds provide scale benefits and reduce cost– but the BIG disruption is the potential of a standardized application platform across public and private domains. So, what will this do?

For handphone applications, user generally does not want to input user id / password each time when they initiate the application. Good design should allow user to input information only the first time.

How to implement it for Android application? Maybe you think it is cookie or session. No, it is another certification – Oauth.

Often times, a client will bring to me a great idea and ask for an estimation. The problem is, for me to make a good estimation, I need to imagine the product from the back: at the last day of delivery, looking back to the project start, what happened? I need to also be able to see the product on that day. "How many buttons on each page and where did they go." All of this gets put into the estimation.