• Developers going indie

    Over the last few years, I've read about a number of developers that have "gone indie" in that they left their jobs and are now independent developers. Maybe make it sound glamorous that they no longer have a boss. While this technically may be true, they still have to answer to someone, be it their clients or their customers. There is nothing inherently wrong with being independent, but thinking that doing this will make all of someone's work problems go away is misleading.

  • Review: Mophie Juice Pack Air for iPhone 5

    One of the problems with any battery operated technology is that it is completely useless when the battery runs down. This, of course, has lead to a huge industry of aftermarket battery packs and charging mechanism for every gadget we use. While I'm not a huge user of my iPhone, I have found that when I travel, I am a little more cautious about using my phone for fear that I'll run out of juice on my phone and not be able to make an important call or will miss a message from home at the end of the day.

  • Wrong definition of a pioneer?

    The other day I was looking at a website of a contracting company that specializes in mobile development. The site said that they were pioneers in the field. The site then had as its next line that the company was started in 2009. I normally think of pioneers as people who initially settle an area or who are first in a particular field. Unless my history of mobile is a little off, 2009 is a bit late to the party. If we just consider the "modern" era of mobile development that began with the iPhone and Android, they are still late as the iPhone was released in 2007 and the SDK in 2008.

  • Flaws in RESTful response codes

    Anyone that uses or develops APIs is familiar with REST. It is widely used and by some developers considered superior to other ways of doing APIs. Since REST was developed alongside the HTTP 1.1 spec, HTTP status codes are generally used for responses to REST calls.