The book has only been available for a week or so, and I am already sick to death of this marketing stuff. I wrote the book. Proofed the book. Edited the book. Got the book up for sale. At this point in the process, the creative part is over and my heart has already moved on to another project where I can be creative. But instead I-
Oh? I didn’t give you a link to buy the paperback version, did I? Sorry. You can get The Witch Watch in paperback here. Where was I? Oh right, angst…
So here I am promoting this thing. In a perfect world, everyone who wanted the book would buy it. But this is an imperfect world, and there are people out there who would enjoy the book but don’t know it exists yet. So I have to spend time getting their attention and describing the book in the best possible way in the fewest number of words. The engineer in me doesn’t like this process. It’s unseemly. It’s like bragging. If I write software-
What? Amazon print version? Yeah. I guess I should explain that. Right now the book is available on Createspace. We have submitted the book to Amazon as well, but it takes them a bit longer to do whatever it is they feel they need to do. If CreateSpace isn’t available in your part of the planet, then I beg your continued patience. The Amazon print version should appear next week. Anyway…
Like I was saying: If I write software, it either meets the specifications or it doesn’t. It doesn’t matter if I run around the office and TELL people the program works. The proof is in the execution, and no degree of psychological hype will alter the output. But books are annoyingly analog in their outcome. It’s perfectly possible to write a terrible book that does well. It’s also possible to write an excellent book that does poorly. And the only way to avoid the latter fate is to talk about your work through a metaphorical megaphone, focusing on the positive and ignoring the negative.
Again, as a coder this is the opposite of what I want to do. I’d much prefer-
Oh, right. I should mention that the print version is $19.99 USA BUX. The book is also available on the Kindle store if you’re down with digital versions. And you can get it on Smashwords if you’ve got a Nook or you want to get a PDF version or whatever.
I’d much prefer to go all post-mortem on the book and deconstruct the writing process, what could have been better, the difficulties I faced in writing it, and the stuff I left out. But apparently discussing your book as a series of mistakes, blunders, failures, and missed opportunities is a bad way to build excitement. Or so they tell me.
Please enjoy the book. Or don’t. I mean, I’ve done what I could.
UPDATE: So now it’s available on Amazon. In print. I don’t know why they said it would take 5 more days. Don’t ask me. I suppose you’ll be wanting the link. The Witch Watch
So what happens when a SOFTWARE engineer tries to review hardware? This. This happens.
Denuvo and the "Death" of Piracy
Denuvo videogame DRM didn't actually kill piracy, but it did stop it for several months. Here's what we learned from that.
Fixing Match 3
For one of the most popular casual games in existence, Match 3 is actually really broken. Until one developer fixed it.
The story of me. If you're looking for a picture of what it was like growing up in the seventies, then this is for you.
Trusting the System
How do you know the rules of the game are what the game claims? More importantly, how do the DEVELOPERS know?