Interview with Keith on mac 20 Questions

Mac20Q Podcast 47 Keith Blount

I got talking to Keith Blount the developer of Scrivener, the excellent writers software.

He tells me that he is a wanna be writer and a coder but not necessarily in that order. Used to be a teacher in primary school and gave up the high life to be a code monkey.

He suggests some books in the podcast and I may well get them myself I would love to be able to write a Mac application. I still want to have a go at writing an iPhone application too. Books by Stephen Kochan Programming in Objective-C 2.0 (2nd Edition) (Developer’s Library)
Aaron Hillegas Cocoa® Programming for Mac® OS X (3rd Edition)

Talking about Scrivener
The idea behind Scrivener is that you write the long novel in chunks and you can use Scrivener to organise the whole thing. there are loads of ways of looking at the work. You can just concentrate on the small bit you are working on. You can see all of the small bits in an outline mode or you can see them on a corkboard view. Lots more information from Keith about Scrivener in the podcast.

He changed to Mac and was looking for a decent laptop and was blown away by the iBook and the retail store experience helped him to make the decision to buy. I have a number of questions for Keith in the interview about how he uses his Mac and you can listen to the podcast to get more.

Win a copy of Scrivener
The question to answer is Is there something spooky in the Text Menu

Many thanks for the interview, David - it was great talking to you.

I have just learned that not only do I like swinging on my squeaky chair but I also say “to be honest” way too much. :slight_smile:

All the best,

Nice interview, though I missed some questions. For instance:

What’s your opinion about word processing on the Mac (and word procession applications for the Mac) in general?

Where do you want to take Scrivener to in the coming years? Do you have any idea in which sense Scrivener 3.0 or 4.0 will be different from the present version?

What kind of future do you see for yourself as a developer? Which ambitions do you have?

But that’s perhaps for the next interview!