apple3

When I first downloaded the latest iOS 9.3 to my iPhone 6s, like most people I was excited to see the new features.  And like most early adopters of technology, and a software developer myself, I was also strangely excited to see if I could be one of the first to find any bugs in the new system.

Like many other people, one of the first “Undocumented Features” I found was that links no longer worked on my phone.  Not just links from a web browser, but any links.  Inconvenient, yes. End of the world, definitely not.  Of course I reached out to Apple to see if they had a work around (which it was too early and they did not).  I jumped on Apple Bug Reporter and logged a ticket and attached stackshots.

In the end, from the March 22nd release date until the March 31st 9.3.1 patch that resolved the issue, Apple was able to receive reports, identify the issue, design a solution, test, and release in just over a week.  While that may seem like a long time to an everyday user, it’s actually quite impressive.

In fact, one of the first things I tell clients when I engage in a project is that we always need to plan for bug fixes and remediation because there will always be bugs.  It’s a fact of life in software development and technology as whole.  Could you build a solution that is 100% bug free.  Sure, but why would you want to?  If you build a system that is 99% bug free, that means you’ve also built a system that is is likely 0-1% innovative.  With great innovation and improvements comes that task of iterating through improvements.

So what is the moral of the story here?  Well first, if you are not one of the 2.5% of innovators or 13.5 percent of early adopters of technology you probably want to hit the “Not Now” button when you iPhone asks you to update to a major release (major releases have just 1 decimal point like 8.0 or 9.3).  If you are a tech-nerd like me than dive right in and enjoy the ride.  There’s something to be said for being one of the first to find something new!  Cheers!