Kevin Hoffman's Blog
Went to the developer program site a few minutes ago and saw the following
We have decided to drop the non-disclosure agreement (NDA) for released
We put the NDA in place because the iPhone OS includes many Apple inventions
and innovations that we would like to protect, so that others don’t steal
our work. It has happened before. While we have filed for hundreds of patents
on iPhone technology, the NDA added yet another level of protection. We put
it in place as one more way to help protect the iPhone from being ripped off
However, the NDA has created too much of a burden on developers, authors and
others interested in helping further the iPhone’s success, so we are
dropping it for released software. Developers will receive a new agreement
without an NDA covering released software within a week or so. Please... (more)
When we all build websites, usually we're concerned with figuring out how
we're going to get the major entities into the view. We want to know how
we're going to handle the shopping cart or how we're going to get the
customer record onto the page, etc. But, one of the little details that
almost always comes back to bite us in the ass is the use of reference data.
Reference data is data that rarely changes, is frequently queried, and shows
up in multiple places throughout the application. This might be anything from
the list of companies currently trading on a particular stock mark... (more)
iPhone Summit at Cloud Expo
One of the biggest problems developers have when building apps for the iPhone
is memory violations.
A lot of developers, especially those who come from a Java or .NET
background, have trouble adjusting to an environment where they need to
manually keep track of reference counts and they need to be explicitly aware
of their own memory management.
I've known quite a few developers who tried their hand at programming for the
iPhone and they threw up their hands and quit when they started trying to
track down memory problems.
I'm certainly not condoning ... (more)
Before you read on through this blog post, check out this post on Slashdot
from a disgruntled Android programmer who is fed up with having to maintain
multiple different code paths to deal with the out of control fragmentation
in the Android market.
First, as great as Java may be, it has never been, nor will it ever be, the
"write-once-run-anywhere" language that its original creators envisioned. So
that's already 1 strike against keeping fragmentation at bay - developers
might be writing Java code, but the underlying JVM and the hardware
availability of Java method calls is goi... (more)
I have been guilty of underestimating the power of Features. It wasn't really
until I started digging deep into the bowels of the new Features and
Solutions system in SharePoint 2007 that I finally started to realize how
pervasive this stuff is. At first glance, it's extremely easy to make a
sweeping generalization that Features are just a simple ability to add
"stuff" in a couple of different locations throughout SharePoint. SharePoint
actually does a really good job of hiding its own use of Features, which
makes this misunderstanding all the more easy to make.
When you create ... (more)