All posts by Mark

I’m the founder of The Hawaii Project, a new book discovery engine. Previously I was responsible for Product Strategy and Product Management at Telenav, after they acquired goby. Prior to that I was the ceo of Goby, since acquired by Telenav. Before that I did time at Endeca, PTC, Netezza, Evans & Sutherland in a variety of R&D, professional services and business development roles. When I’m not obsessing over work, I’m a proud husband and father of two great kids, love to play tennis, am a compulsive reader and book collector, and am really into way too many different kinds of music. (What’s with the Viking you might ask? While the vikings were known to split a skull or two, I mean more the verb than the noun, as in “to go adventuring” in the sense of the Old Norse fara í víking. I’ve always been interested in the vikings and started using viking2917 as a handle to avoid spammers way back when, and have just kept using it….)

The Rules

Leroy Jethro Gibbs of the NCIS TV show has a pithy set of rules.

Here’s my version, adapted for life in the professional/startup world. (some of these are a bit cryptic – someday, blog posts for each of them).

  1. Leave your politics at home.
  2. Gibbs is wrong (Gibbs rule #6). Apologizing doesn’t show weakness, it shows strength. If you’re wrong, admit it.
  3. Do something every day to earn your team’s loyalty.
  4. Hire your own damn people. HR won’t do it for you.
  5. Somebody on your team will always make more money than you. Get over it.
  6. Never confuse selling with implementation.
  7. Time is my most valuable commodity. With respect, get to the f’ing point.
  8. The deal’s not done til the money’s in the bank. And sometimes not even then.
  9. Feed the troops. An Army runs on its stomach.
  10. Equal pain for all. unpleasant task = everybody helps.
  11. Don’t forget to manage up.
  12. Take care of your stars. I mean, really take care of them.
  13. Always return emails & phone calls
  14. Honor your mentor.
  15. One hour a day, one day a week, don’t think about work. Harder than it sounds. Do it. (I learned this from my mentor).
  16. Every opportunity prepares you for the next one. (see rule #5).
  17. Bad news first. Good news is fun but there’s nothing actionable about it. Bad news, you can try to fix.
  18. When you have to make a decision, think carefully, ask for opinions. Then make a decision and don’t change your mind. (Indecision is fatal in a leader)
  19. Never let the facts stand in the way of a good story.
  20. Hire adrenaline junkies.
  21. Rip off the bandaid.
  22. Never make a decision until you have to. (My take on this, via Shogun, a master class in this).
  23. Always carry on your bags; never take a connecting flight (wait – that’s two rules)
  24. Never release on Fridays
  25. Don’t fight the last war. (re: when we built goby, we focused on our website even as mobile was becoming ubiquitous)
  26. “Your reputation is important and easily damaged, and people talk”.
  27. Remember, you can always say “No”. Later. (ie. don’t close things off too soon – you don’t have to commit just because you take the meet or offer the phone call….).
  28. “Hands and Feed Inside the Vehicle at all times.”. Enjoy the ride.
  29. Next slide. “Great Launch! Next Slide”. (from my first post-launch goby board meeting, after I showed the celebratory slide in the board meeting. One of my board members said this almost as soon as I put up the slide. The point: be future-focused and keep driving for more.)
  30. Paraphrasing Gibbs: When the Job’s Done, Walk Away. (when you step out of a job, don’t take another one for two months if you can help it. Your brain will change.)
  31. Be (civil) In The Arena. (re: Roosevelt quote). The Arena is The Internet and Social Media. As a leader of your company, be present. Don’t be afraid to respond to your critics as well as your friends. But be civil. Flies, Honey, Vinegar, etc.
  32. The three laws of email (with hat tip to Asimov’s three laws of robotics)
    1. Never send email when you’re mad.
    2. On the third reply, use the phone.
    3. Reply All is not your friend.
  33. Always close the loop on an intro. (if I introduce you to a VC, let me know how the meeting went. Who knows, I might have back door info….plus, it’s just polite).
  34. If you’re going to eat shit, don’t nibble. (originator: Ed Gillis @ PTC)

Further Rules reading: George Washington’s Rules, Fred Harvey’s Rules, Rules I gleaned from Steven Pressfield.

The Never Open Desert Diner by James Anderson

Ben Jones drives a truck in southern Utah. He’s damn near broke, about to lose his truck, and his best friend is Walt, an old guy who owns a diner that’s never open and barely speaks to him (think a grumpy Robert Duval).

Ben is a pretty normal blue collar guy, but with an occasional penchant for the philosophical:

Below that was a rising shiver of cold desperation. Things had to change. I wanted them to change. Like most people who said they wanted change, all I wanted was enough change to keep everything the same, only better.

The Never-Open Desert Diner

BEN JONES, the protagonist of James Anderson s haunting debut novel, The Never-Open Desert Diner (Caravel Books, February, 2015), is on the verge of losing his small trucking company. A single, thirty-eight-year-old truck driver, Ben s route takes him back and forth across one of the most desolate and beautiful regions of the Utah desert.

Walt is the owner of The Never Open Desert Diner, which author James Anderson places on Route 117, crossing route 191 near Price. Having lived in Utah and driven 191 down to Moab many times, I can only think Mr. Anderson is toying with us, as 117 and 191 don’t cross so far as I know. There is an old diner (my friend Thomas says it was the Sky Cafe Diner between Spanish Fork and Price, which might have been the inspiration?).

Except for that, Anderson gets southern Utah almost pitch perfect. The silence of the desert, it’s emptiness and it’s deadly beauty if you’re not prepared for it. The quick change from a clear sky to ominous clouds to a thundering, drenching rainstorm in a matter of minutes.

Never Open Diner starts pretty prosaically, but soon Ben is wandering into an abandoned house in the desert and stumbling upon a naked woman playing a cello with no strings. It feels like it’s about to become an urban fantasy (well rural fantasy) novel, but it actually never becomes unreal, just a fun ride involving a mysterious woman, a horrible event, a film producer and a stolen cello. There’s a great cast of characters, by turns intriguing, infuriating and enchanting.

It’s really good fun.

You can find more here: http://www.thehawaiiproject.com/book/The-Never-Open-Desert-Diner–by–James-Anderson–100720

(I received an advance reader copy of this book from the Library Thing Early Reviewers program)

Anatomy of a Hack – Books, Music & CODEX

Awhile back I randomly found out about CODEX Hackathon, a “literary hackathon” mashing up books and technology, and I knew I had to get involved. I started by registering to attend, but realized pretty quickly I wanted to do more. I volunteered to helped organize and sponsor, which I’ll write about later. I also hacked, and wanted to share what I came up with, and how I came up with it.

I’ve been interested in the intersection of books and music for awhile. I used to write book reviews with embedded playlists of what I was listening to while I read the book. Or make playlists of music mentioned in a particular book – for example, the early jazz mentioned in Kathleen Ann Goonan’s In War Times. Or read interviews where authors talk about the music that inspired them as they wrote.

And write why Books & Music go together like Wine & Chocolate.

Books & Music: Like Wine & Chocolate

Books and music go together like, well, wine & chocolate. Settling down on the couch with a great book, a glass of wine, and some great music has to be one of life’s guiltiest pleasures. Heck there’s…

So when this hackathon came along, the juices had been flowing for awhile and I knew what I wanted to do. Build an environment where people could collaboratively build and share music playlists for their favorite books.

I had the basic idea framed out in my head. I’d use the Spotify web player and hack up a branch of http://www.thehawaiiproject.com to become the new thing. Seemed like a layup, all their Web APIs are sitting right there. Spotify has a feature for “collaborative playlists” – what could go wrong, right?

After some presentations from sponsors (I was a sponsor, here was my pitch for The Hawaii Project), we get down to it, at 11am Saturday morning.

Here’s a quick timeline from my notes:

start @ 11
around 12, have a Master & Commander (Patrick O'Brien’s book) page with a static playlist on it. Everything hard coded but I can listen to music for the book and it visually looks pretty good!

My plan is to use Spotify’s Collaborative Playlist feature so everyone can add to the playlist (and be authenticated to Spotify in the normal way via their browser). SNAG! Turns out making a Playlist “Collaborative” in Spotify makes it Private so only collaborators can see it. Even worse, via the API, only the Owner can modify it. That pretty much blows the whole idea out of the water.

OK, Plan B. I will make a Hawaii Project Spotify account that will own all the playlists. When users add an item to a playlist I’ll send it to my server and the server will add it to the playlist. Because the API calls have to authenticate (via OAuth) to the Spotify server, I have to figure out how to authenticate in PHP to Spotify without a browser around. I dumpster dive in Stackover flow and find The Hint (thank you Michael Thelin!).

12:00 : 1:30pm. I struggle to get The Hint to work in practice. I take a break and grab lunch (wonderful sandwiches and Hummus, CODEX has great food!).
3:41pm EUREKA!!!! I get a valid spotify token and successfully retrieve a playlist!!!!!
3:42pm. My token expires and I can’t figure out how to get it to renew.
7:45pm. I think I get a repeatable way to add tracks, at least until my token expires. which I have to renew manually. OK for a demo but can’t actually go live with that. I’ve spent ~50% of my hacking time on OAuth. Not what I had in mind.
8:30pm. I have some basic track search + autosuggest for tracks working. (like when you type “Stairway to H” I suggest “Stairway to Heaven by Led Zeppelin”)
8:50 Stairway to Heaven and Highway to Hell added to playlist via UI. !!!!!!
9:50 Code cleanup. Things basically working with a single hard-coded book & playlist ID, except hacky tokens & expiration.
10:00 Did I mention this is a hackathon for Adults? MIT kicks us out at 10pm. Home. Martini. Sleep.
Sunday
6:30 am up, by 7:40am On the train.
8–9 in coffee shop because MIT doors locked. Quickly solve some problems with playlist views and track list ordering problems solved. still struggling with expiring oauth tokens.
10:00 With the exception of tokens, I have what I need for a workable demo, can search for and add tracks to any book.
10:30–11. Make some fun playlists for some of my favorite books!
11:12 roll a new home page showing the latest books that have soundtracks created.
12:30. stop and roll a deck for the presentation.
1pm. Hands off the keyboard at 2pm for presentations, so I decided to adopt the “Vietnam strategy”. Declare victory and get out. I avoid breaking my demo with any late changes, and go chat with a few interesting folks I didn’t have time to get to before.

Presentation went well (in fact everyone’s did!). I start my presentation with the James Bond theme and end with adding Highway to Hell to a playlist, and playing it over the speakers as I exit. Mission Accomplished.

I wanted to launch it to a live URL during the Hackathon, but I just couldn’t solve the expiring token. On the drive home, I decided that tomorrow I’d ask my son-in-law, who is an actual practicing software engineer. But I wake up the next morning and, as often happens, within about 20 seconds I see a typo that’s been causing me all this grief. Edit, “git commit -m “I’m an idiot””, and a few minutes later, voilá: BookPlaylist is born!

As I write this, I’m jamming to Kayti’s most excellent playlist to Cinder, a book I’ve not read. But now might.

Cinder (Lunar Chronicles)

It was really fun to take an idea that I’ve had in my head for almost a year, and get it out of my head and into something real. Hope you get a chance to play (pun intended) with it!

You can read a bit more about the Hackathon here (via Matthew S Carroll, one of the organizers.

Welcome to the CODEX Hackathon 2016

Hello, from the the CODEX Hackathon. We’ll be live blogging here all weekend, so come back often as we update. To follow on Twitter: #codexhack. The hackathon is about…

In later posts, I’ll write about the technical tools we made available for participants.

A few months with Scribd

oysterWhile I’m a bit late to the game, I’ve spent the last 3 months exploring the subscription model for ebooks. As you may have heard, the inventor of the concept – Oyster – shut down awhile back (Amazon has Kindle Unlimited now). I’d given up on Oyster previously because they never had the books I wanted to read. I’ve previously suggested I think the end is coming for the subscription model, and offered a few ideas for how to save it.

Scribd has become the “last man standing” in terms of a standalone ebooks subscription service. I decided to live with it for 3 months to see how compelling I found it. Here’s my experiences and thoughts.

  • The Reader is very nice.
  • The Catalog isn’t deep enough — it’s “OK” but not compelling.
  • Some interesting browsing and categorization
  • Onboarding is only so-so.
  • Personalization is cumbersome, and the recommendations are lacking (but I did bring me a few winners.
  • No Community.
  • $10 a month isn’t quite worth it.

Before diving into details, here’s the punchline: it’s a good service, I read some good books and enjoyed it, but I don’t plan on keeping my subscription going, as the service stands today.


The Catalog

The first and biggest challenge of the subscription model is the depth of catalog – do they have the books I want to read? Because this model isn’t as profitable for the publishers, they limit which books are available.

By virtue of my book discovery engine (The Hawaii Project), I have a TBR (To Be Read) list as long as your arm. I’m an eclectic reader – my TBR list is a mix of espionage thrillers, historical fiction, literary fiction, a few bestsellers and a smattering of non-fiction – bios, arts books and the like. My list is biased towards more recent books, but contains many classics and older books that are waiting for their turn.

So, how does Scribd fare against my TBR list? An analysis showed that 19% of my TBR list was in there — mostly the lesser-desired books, and older books. The more obscure the book, the more likely Scribd had it. I’ve been dying to read the new bio of John Le Carre, All The Light We Cannot See (one of 2015’s most highly regarded books), and A Crown for Cold Silver, a highly regarded 2015 Fantasy novel. Struck out all around, and on most of the books at the top of my list. The books Scribd were sort of my personal “back catalog” – books I wanted to read, but not bad enough to buy just yet. There were some goodies in there.

Over the course of the 3 months, I read from my TBR list – A Sport and a Pastime, the first classic from James Salter I’d been meaning to read for some time. Whale Road, a Viking novel. Solo, a James Bond novel by an author I love, William Boyd. A truly great book, A Death in Veracruz, a translation of a book by Héctor Aguilar Camín about the Mexican oil wars. Ride a Cockhorse by Raymond Kennedy. The Flamethrowers by Rachel Kushner.

While I think Scribd’s discovery methods aren’t that great, it did manage to unearth a few treasures. I thought I knew every book Bernard Cornwell has written, but Scribd brought me Scoundrel, a sailing novel, which was good fun and unknown to me. And The Far Arena, a truly wonderful Roman gladiator time travel novel. And a few others. So, I read 10 books, for the cost of $30 (3 months of Scribd). Not bad, although I could have bought those books used for about the same price, and wouldn’t have bought them new (or maybe at all) as they weren’t at the top of my list.

Finally, they had a pretty deep Audiobook section – many of the books they did not have in written form, were available in Audiobook form, so if you’re into audio books you might have better luck.

The Experience

I found Scribd’s reader to be very nice. Clean, minimalist and easy to use. I wish I didn’t need another reader (competing with Kindle, iBooks, etc), but it’s easy to use.

Browsing for books is nice, from a user interface perspective (although I think The Hawaii Project’s is better :)). In addition to the usual categories like Literature and Fiction, Biography and the like, they have some interesting sub-genres, Netflix-like, for example, “Set in San Francisco”, “Identity Crisis”, “Muskets & Magic”, “Nordic Noir”, beyond the rather formulaic categories one finds on Amazon or Barnes & Noble. But the books shown in the major categories aren’t the ones you’re looking for, because of the catalog issues.

I found the onboarding process, and the personalization and customization, to be awkward. Since so many of the expected books are missing from Scribd, it’s essential for them to bring me great personalized recommendations, and to make it easy for me. It wasn’t. It was quite awkward to quickly tell them about the many books I’ve read recently, and as a result I’d already read most of the books they recommended – and there was no quick way to tell them that or get them to stop recommending it. A simple checkmark on each book cover would have done it.

Last but not least, there’s no community to speak of on Scribd. I get that it’s a reading platform, not a social network, but in order to survive with a limited catalog they need something to make it sticky. Reddit’s book community is vibrant and millions-strong. Goodreads is the defacto book community and that’s what keeps it going. Scribd needs something besides just a reader to keep going.