A few years ago I was subcontracted to one of the large consultancies. I was taking over from someone who was, supposedly, quite senior and the task at hand, I was told, was very hard. I should take copious notes as she wouldn’t necessarily be around afterwards to help me. Making a mistake or missing out any one step could be disastrous to the whole process. If I did everything properly each new installation would take about a week.

I’ve had my iPhone for over a year now. O2 have got more money out of me than they really deserve given how much I actually use it as a phone, but overall I’m still very happy with it. This is all the more surprising when you consider that I’ve been disappointed with pretty much every phone I’ve had over the years. The last one I was actually happy with was a Nokia 6310i, one of those boring but ultra-competent devices that basically just works. I even got nearly two weeks on a single charge; I barely get two days on the iPhone.

This is probably the meanest article title I’ve ever written, as the “W” refers to a person, someone that I used to work with¹. The critical phrase went something like this:

“How hard can it be? It’s only a button!”

Those two, tiny sentences hide a lot. Let me explain.

I’m mainly technical. I have been in the industry for over ten years now, did a computer science degree and spent many hours when I should have been revising for my German GCSE programming my Sinclair Spectrum. This means that when someone says “It’s only a button” I instinctively cringe. I may not know the details but I’ve seen enough “simple” buttons with days worth of work behind them that I’ve learned to be cautious.

Here’s an exchange that occurred just the other day: colleague A asked colleague B for some help in PowerPoint. B says, “It’s easy, I’ll show you how to do it.” A immediately objects: “I don’t want to know how to do it, can you just do it for me?”

The dialogue continued for a while, with A not happy to have to learn something new and B not happy to become A‘s lackey.

What do Britney Spears and Yummy, my iPhone Delicious.com client, have in common? If you had asked me a few months ago I would have said nothing but I’d have been wrong. No, they both have had to grow up in public.

For a version 1.0 product, Yummy seemed solid to me. It was fast, coped will all my bookmarks and had the ability to add, edit and delete entries. I didn’t think that this would remain as a unique feature for as long as it has, but hey, that’s a bonus.

My iPhone application, Yummy, has been on sale in iTunes for a couple of months now and, as a number of other developers have noted, after the initial launch sales figures take a significant nose dive very quickly. I’ve been trying to think of ways to increase visibility without taking too much time away from actually making enhancements to the software.

As luck would have it, I got a “free trial” of Google AdWords and thought I would give that a try. Results have been… well, not exactly what I was expecting.

It’s been over five years since I last told you about my favourite computer and programming related books (don’t believe the date on that article. It’s been edited lightly a couple of times since I first posted it).

Having said that, some things have not changed. The vast majority of books on the shelves of your local retailer are very specific. Publishers seem to eschew broad, generally useful texts in preference for yet another beginners guide to Microsoft Word or C++ (or, more likely, Visual C++ 2005 Special Easter Edition SP2). I do not understand this. Sure, there’s a genuine need for “how to” books for specific technologies but is it not more useful to learn how to solve problems in general rather than how to solve a particular problem with a particular product?

As many readers know by now I am in the late stages of developing and releasing an iPhone application. This is the first time I’ve ever really been involved in the launch of a consumer product and while there’s nothing here that is likely to surprise any marketing guru’s, I’m finding it an interesting process.

I talked about pricing previously, but today I want to talk about the competition.

I downloaded the SDK¹ shortly after the original announcement. The first version was fairly primitive, with little to no support for the drag-and-drop style of development used for parts of Mac OS X programs. I played around a bit, compiled a few demo applications but didn’t really get very far. Too hard, I though.

This originally started as a question on Apple’s support boards:

With the current AppStore model (which seems to be a money machine for developers) I do not understand why anyone would give away their applications. At least charge $0.99 and get something back for your hard work.

So, why do you give away your apps?

With the caveat that I have not actually submitted anything yet…

My motivation in writing an application was entirely for the pleasure of doing it. If I never do anything with it once it’s “finished” my goals have been achieved. So my only objective in pushing it to the AppStore is for other people to get some benefit from using it too. There is little incremental cost in doing so and zero cost means that it gets the widest possible distribution.

I’ve not done much programming in the last few years. When I first started working my job was mainly to “cut code” but I’ve done less and less as time has gone by. I now tend to concentrate on high level modelling and writing small utility scripts. I have not been doing much at home either, just minor tweaks to pre-existing software to “scratch an itch” or programs to automate tedious tasks.