I’m no stranger to writing. I’ve published a couple of tech books, and I’ve a novel being edited, so I know the idiocy of writing a book. No need to go there.
redis, imo, is one of the great technical tools of the last decade. Outside of a small percentage of projects (e.g. big data proper), I believe that postgres and redis are all you’ll ever need for your data. Yet, wherever I go, I see folk using redis as a kind of memcached+ (usually implemented in a painfully tortuous way). It’s often regarded as a caching tool and not a blazingly fast db with a phenomenally diverse range of data types providing hereto unforeseen solutions. Madness! redis rocks! Have you actually used expire?
So, I started sketching the outline of a book about redis aimed at developers. The only things I’ve settled on, so far, are that I want to consider redis’ operations in their discrete groups. i.e. strings, hashes, sets, geo, hyperloglog, etc., and I want it to provide some sort of reference.
Beyond that, I’d really appreciate ideas, thoughts and suggestions from folk here.
 The others are git and ruby, and I’d wager on elixir being in the same category.
 I’m considering Leanpub for publication. (I rejected them in the past because they only support dropbox (which I won’t touch) and github (which doesn’t work for me).