by Joe Zhou

Here are the most interesting articles I read this week:

1.       James Donelan at MuleSoft shared his takeaway on designing a perfect API. http://bit.ly/1eO4E9L

·         Keep it simple and follow REST principles.

·         Give a developer lots of control and flexibility in using your API.

·         Consider how navigation across data and the APIs will work.

·         Support versioning from the very beginning.

·         Keep your API up to date and constantly leverage new standards.

·         Protect your API and keep it secure.

·         Provide great documentation for developers and keep it up to date.

As Joshua Bloch said in a keynote he delivered 8 years ago about API Design, you have one chance to get it right. Otherwise, the API becomes a liability as opposed to a great asset.

2.       QA gets paid to test or break software developers write. That doesn’t necessarily mean developers can get away from testing their own code. Here are ten things developers need to think about when testing their software.http://spr.ly/6015jWCN  

1)      What is the purpose of the tests? Might be purely function, performance (speed, space, etc.), accuracy.

2)      What are the risks of inadequate testing?

3)      Can I bring any of my testing in earlier?  (This is probably the single most effective money saver in any software program)

4)      Have all the requirements been covered in the software and the tests?

5)      Is the software, or this piece of it, ready for testing?

3.       The Native APP vs. HTML5 debate will be going on for a long time. SD Times knows what goes well with HTML5 and who is taking the lead right now. http://buff.ly/1gWtRAC