One of the last hot news that is triumphed all over the blogs is that now there’s a free iPhone unlocking app available for download for anyone. People in US can buy an iPhone from AT&T, remove the SIM-lock, and use the phone also with other GSM networks like t-mobile etc.

I’m pretty sure I  know what Apple will do now. They will release iTunes *.0.1.2 of whatever, which will effectively update your iPhone in a way that the SIM-unlocker wont work anymore. Then we will see another (updated!) version of the unlocking app, and yet another iPhone firmware update from apple. And so on, and so on… Of course, some people say they will not update their iPhones, but eventually I’m sure they will be forced to do that - simply because at some point there will be some security patches or cool features that they _definitely_ want to have.

The single fact that is helping apple on this crusade is the nature of things - things change. Constantly.

And one of the funnies places to observe that crucial law of things are web projects. I’ve managed tens of various (large and small) web projects by now, and in many cases I can see exactly the same symptoms -  client wants to make a project X by deadline Y. After that, client wants the project to be “done” (permanently)  and we should just install it on the server and “let it live & grow”.

What most non-IT people doesn’t realize however, is that in IT just like everywhere else - things are changing. OS systems get updated. Programming languages as well. With critical fixes - so you just HAVE to make the update - even  if it effectively mean breaking your web app. Or with major version  releases, and abandonment of older version (like PHP4 being not supported by PHP community anymore). This means a constant flow of work  for IT people and a headache for clients - but hey, thats the nature of things as well

If you build a web application you can be sure of one thing. It will change. Updates will appear to the whole surrounding IT environment and you get forced to update it. Some additional expertise might be needed (read: costs). Its never the case that you just build it and its “done”. And the quicker you realize that, the less surprised you will be when you get yet another email from you ISP or IT team saying that “we need to update this and that” even when you thought that “that thing” is working just fine…