• Developing iPhone applications with teams

    In my last post, I identified a number of areas that make developing iPhone applications with teams problematic and sometimes difficult. In this post, I'm going to present some of my ideas on how to make it easier.

  • iPhone Development and teams

    Since I've been self employed again, I've been working on 3 iPhone development projects. On 2 of the projects, I'm the lone developer (at the moment), with a QA resource and a project manager. On the 3rd project, at its peak, we had 5 developers, 7 or 8 QA folks, and a project manager. This last project has made it painfully obvious to me (more so than the other 2), that Apple has designed iPhone development around the loan developer that has no formal QA.

  • Abstract Photo

    My son loves playing with our camera and takes lots of pictures. Most of the pictures are blurry and we delete them. However, sometimes he takes a picture that looks pretty good. He was playing in my office a few months ago and took a picture of the mouse pad (a funky HP one; it was the largest one I could find with a smooth surface).

  • Open source is not always the answer

    I've been a huge fan of open source software for years and have contributed back to a few projects including the Palm OS Emulator and pilot-link. I've used a number of open source projects in my own applications and, of course, follow the license for attribution (I don't touch GPL code). Years ago when I was a lot greener, I used open source thinking that it must be perfect and treated the code at black boxes. This bit me on at least one project where we had to fix the code for years due to assumptions by the developer.