It’s now been almost six months since I joined Code 42 Software as VP of Marketing. Having a ‘regular’ job, where I actually drive to the office every day, has been quite an adjustment for me. Until this, I’ve more or less worked from my home office for the past 25 years. That meant I could be lazy when I felt like being lazy; an option I definitely used from time to time.
But that’s all behind me now!
I’ve always loved being involved with helping products and companies grow, and at Code 42 I get that in abundance. Being immersed in the creative process again has helped to clear some cobwebs and brought me back to thinking about this book I’m supposedly writing. Further, thanks to some prodding from a few esteemed friends, my confidence is returning and I’m starting to feel like I can get back to work on it.
This feeling is not without counterpoints. Given Steve Job’s poor health, I don’t want to be seen as engaging in the rumor-mongering and uninformed speculation that has become so commonplace. My intention for the book was always to make it about my personal journey from admiring Apple from afar to being unexpectedly in the middle of the action, and continuing on to my more recent adventures. I didn’t want to write a book just about Apple or just about Steve Jobs. (I never felt I had enough ‘hard data’ about either to fill an entire book in any case.) And the closer we get to a world without Steve Jobs, the less interested I am in sensationalizing any part of my related experiences. And all along, I wondered if my meager writing skills are up to the task of describing how Steve or Apple do their respective magic.*
Which brings me to the ultimate question of life, the universe and everything: will I ever finish this damn book?
The answer is a most-definite probably.
*a good friend, who happens to be a writer, pointed out that entire -good- books have been created by basically padding a one paragraph story. He humbly suggested that maybe I was demanding a bit too much journalistic rigor for a project that doesn’t require it.