Apple are announcing their new iPhones tomorrow. Along with the new phone will be a new version of iOS, version 9. You can read all about what Apple thinks are the best new features. I’ve been using it myself for a couple of months now so I thought it might be worth a few words.

Here are my highlights:

• Battery improvements. Actually, they say you get an extra hour but I’ve not noticed. What works great is Low Power Mode. When it gets below 20%, the battery icon turns yellow and lots of stuff gets turned off or the frequency of background tasks is decreased. It’s not magic — if you use your phone it will drop to zero pretty quickly — but if it’s just sat in your pocket you’ll get a lot more life out of it.
• Spotlight search inside apps. This clearly isn’t going to be big until apps support it, but even with my own apps this is really big. I miss it on my iPad 3, which doesn’t support it.
• Looking in your email to guess the names of callers who are not in your address book. It’s kind of freaky the first time it happens. How does it know that this phone call might be from Bob?! But it works and it’s very useful. Oh, and if it can’t make a match it now tells you where the call came from (just as it has done in the US since the very first iPhone).
• Feels as fast, if not faster, than iOS 8 on both my iPhone 5 and iPad 3. After all the press claiming that Apple make big, clunky updates to force you to upgrade that’s nice.

Showing potential:

Share price movements are kind-of-sort-of-rational but not always intuitive. For example, when Apple has a big keynote and announces some significant product, everyone expresses surprise that the share price goes down straight afterwards. Even many smart people get this wrong (“It isn’t based on logic and reason” – The Talk Show episode 53). I hope to explain why the price dropping actually does make sense in this post.

In doing so I’ll likely make some errors. Some of those will be deliberate simplifications. In other cases I’ll probably just be wrong. But either way, I think the gist, if not the details, should give you a good idea of what’s going on.

I never know whether to put blogs about Apple stuff here or on my company website. This time I wrote a few thoughts about the best bits announced at last weeks WWDC keynote (mostly stuff arriving in the Autumn) and put them over on the Wandle Software blog.

It’s easy to forget how much computers have changed over a relatively short. time. A book I found in my old room at my parent house, “Simpleton Explores Microcomputers,” helped me get some perspective.

I don’t know exactly when it’s from, but it’s certainly early eighties. Possibly 1983 or 1984.

It explores the computers that are available at the time and what it’s like to own one. One of the most telling aspects is that it’s written for people who have never owned, possibly used, a computer.

It all starts out with a detailed plan. Then someone says, “Can we deliver by October?” A few features get cut, some of the estimates get revised downwards and everyone gets back to work. Then you get to the end of September and find that someone removed all the contingency and that in the rush to finish the requirements a heap of important stuff got missed.

You spend days, weeks, quite possibly months pushing to get the software developed and, a few months before the real end, a crunch point is reached. It’s missing what’s now realised to be critical functionality; it takes an hour to process something that should be instant; the data doesn’t look like you thought it would; it’s too late for any real benefit to be obtained.

Last week, GitHub was the victim of a days long denial of service attack that meant that it wasn’t available reliably despite the hard work of their team.

What surprised me was the number of people on Twitter complaining that they couldn’t work. I was surprised because one of the key things about Git (the tool rather than the website) is that it is distributed, that is there is no centralised server in the way that there is with, say, Subversion. Clearly there are things you can’t do without GitHub – most obviously downloading new repositories – but almost everything else can be done peer-to-peer. The rest of this post explains how.

“Preview” is damaged and can’t be opened. You should move it to the Trash.

This was the rather surprising error message that I’ve been getting when I try to open a PDF from the Finder since I upgraded to OS X Yosemite. It’s bad enough when you get an error message, but one suggesting that you delete a frequently used app is inconvenient to say the least!

When I read Rand’s recent post on QA I was pretty much entirely in agreement. A good QA team is a real asset to any project, especially large ones. However, a bad QA team can be a huge liability and cause problems for everyone.

Bad testers don’t understand the product they’re working on. They follow test scripts they don’t understand, write short, inaccurate bug reports and make no attempt to appreciate the context of any error.

Ever since upgrading from OS X 10.9 to Yosemite (10.10) I’ve been getting the above error message periodically. As far as I know I have no software that needs Java to run.

When I asked on Twitter, the most common suggestion was that it was the Adobe updater. But I don’t have PhotoShop or anything else likely installed.

Maybe I have some duff feeds in my RSS reader. Maybe I have a few poor choices of people that I follow on Twitter. But I see links along these lines all the time:

How do you do something in Swift?

The answer is, almost always, exactly the same way you’d do it in Objective-C!

You want to do pull-to-refresh? Same.

You want to play with location services? Same.

You want to display one of the new UIAlertControllers? That’s the same, too.