When I think of “Stillness,” this weeks PhotoFriday challenge, I tend to think of a lake; an apparently unmoving body of water. (A lot of the other entries, to my eyes at least, don’t represent “Stillness.” Of course, mine may well miss the mark for them…)

Whatever its merits, this one was taken near Spooner Lake, which is very near Lake Tahoe.

I didn’t have an entry in the last challenge, so there’s no need to vote for me(!).

It’s important to have a Top 10 list. I know this as every other site has one. I don’t want to miss out. So here are the top ten most read posts here this year, with the year they were originally published in parenthesis:

1. QA Mindf**k
2. Do Apple take 40% in the EU? (2011)
3. Learning Swift
4. iOS Developer Program: from individual to company (2011)
5. How do I do “X” in Swift?
6. AQGridView to UICollectionView (2013)
7. iPhone Dev: Saving State (2010)
8. NSFetchedResultsController and iCloud
9. Why you need a crash reporter (2011)
10. Sophia Smith (2006)

If there’s a lesson here in increasing readership it’s simple: get retweeted by people with lots of followers.

Preamble: In pre-Swift and pre-ARC days of development on Apple’s platforms, it was necessary to “manually” retain and release objects as you used and discarded them. One common, but incorrect, pattern that kept reappearing was the idea that you could use the retainCount method to ascertain whether an object was still being used.

## When to use -retainCount? Never!

There’s pretty much never a good reason to use -retainCount. Here’s a short and mildly abusive explanation why.

This weeks PhotoFriday them is “Blue” and these are bluebells (I think), which should count, even though there aren’t technically blue.

I didn’t enter last weeks challenge, so I’m not going to insist that you vote for me. (In fact, the last time I forgot to even vote for myself!)

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.

I had images in my mind of gleaming, bright, shiny metals but in the end, I thought this picture of a rusting cannon in Rhodes Town was a better photograph. And a better photograph is what PhotoFriday is all about!

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.

My entry to this weeks PhotoFriday challenge, “Translucent,” was taken much closer to home than many of my previous ones. It was from Tooting Library which is just a few minutes walk away from home.

Please also vote for my entry in last weeks challenge, “Autumn Colours.” I’m entry number 86.

For some reason, when I saw the poster for the new movie “Fury,” I misread it as “Furry” and saw a beard on Brad Pitt that wasn’t really there. I’ve tried to correct these errors.

I was so busy when it came out that I never quite got around to blogging about it here: I have a new app out! It’s called ShareEverywhere. It is built exclusively for iOS 8 and uses the new, built-in “share” functionality, allowing you to share to a good number of services from any app that uses the standard share button.

When I first wrote it, I wasn’t sure how many, if any, developers would build share widgets into their apps. Now that we know the answer is “a lot of them,” I still use ShareEverywhere because it beats having a dozen widgets hiding in your action menu. And there are still services, like Pinboard.in, that don’t have their own native apps.