Why Apple Chose iPhone Despite Cisco Owning the Trademark

In moments, there will be blog comments all over the Internet about the new iPhone that Apple just released. But I pondered, “Why iPhone? Isn’t that taken by Cisco?”

I’m not a lawyer, but I offer an explanation. I may be wrong, but give my explanation some thought.

The Wikipedia article on trademarks has this clause:

Unlike patents and copyrights, which in theory are granted for one-off fixed terms, trademarks remain valid as long as the owner actively uses and defends them and maintains their registrations with the applicable jurisdiction’s trademarks office.

The key is “defends.” Now do a news search for iPhone. You’ll see a freakishly lame press release about Cisco’s new lame phone, a trademark they’ve owned for a decade. But it’s buried in articles about Apple. People have been speculating for years about Apple’s coming iPhone. Even in 2002.

And yet no word of Cisco ever telling anybody to quit referring to the product as iPhone. None.

Perhaps Apple’s logic is simple: The entire world already thinks of Apple when someone says iPhone and it’s largely due to the fact that nobody ever contested this public perception. Perhaps they intend to argue that the trademark was invalidated years ago.

P.S. For the record, my prediction wasn’t too far off.

Why is Software Development So Hard?

Why is software development so hard? That was the topic of a Slashdot article that was featured today. In short, the article was asking why, after all of the collective experience in software development, is it still notoriously difficult to get quality software out on time, without bugs, and under budget.

On one hand, it’s obvious that software development is still a relatively young “science,” as it has not been around for even half a century. Despite this, the article had an interesting point. Why is it that no matter how many times companies produce new software, they inevitably fall victim to delays. Just look at Vista, the next version of Windows that has been delayed over three years and shed large portions of its original specifications. Less features, more money thrown at the problem, and yet still late by three years? How, you ask?

I am not linking you to the actual article because it isn’t nearly as interesting as this comment I read in response to the question. A clever reader wrote in response:

Why is conducting an orchestra so hard?

Some might read that and think it was a joke. But the next reply put it into context.

It isn’t. Haven’t you seen them, all they do it wave their hands around and look silly. That’s the point. Everyone thinks it’s a breeze when it isn’t, so everyone underestimates everything.

Of course, my sharper readers would notice that these answers don’t actually answer the question. In fact, all they do is dismiss the question by saying, “because it is harder than it looks.” This brings up a very important lesson that seems to elude many companies (thankfully not mine) when it comes to IT project managing. You can’t expect a masterpiece without the talent, knowledge, and experience. Another reader wrote:

A good orchestra conductor who is in front of a bunch of rank beginner inexperienced musicians will not be able to make very good sounding music. You get what you pay for.