writing

I'm not a writer. I'm a software developer who communicates well. Because I'm a developer and software architect, I spend time evaluating solutions to find the best one. There are often multiple good options, but I try to pick the best among them.

When I chose to write a book two years ago, I evaluated whether to self-publish or seek out a publisher. I spent a lot of time evaluating my options, and chose the self-publishing route.

Because I'm asked about this a lot, I decided to summarize my reasons in a blog post, both to posit why self-publishing is almost always the right option for a beginning author, and to challenge publishers to convince me I'm wrong.

Today LeanPub published it's 25th episode of the LeanPub Podcast, and in it, Len Epp asked me about a wide range of topics, including AI, the impact of smartphones on interpersonal relationships, how I got started in computing, and how I self-published a bestseller, Ansible for DevOps, on LeanPub.

A few decent quotes from the interview:

[On how I learned technical/tutorial writing:] Go sit down, sit through all the tutorials, and then write up a guide that will help people to quickly get up to speed on it”. Because the manuals you get with the manufacturer are pretty much junk.

As a technical person I hate the idea of DRM on a book. Because it’s like, when I go to a bookstore and buy a book, I don’t have like a locking mechanism that I have to unlock to read it.

After almost two years of writing, editing, and rewriting my book, I've finally completed the first edition of Ansible for DevOps, and it's available for sale on Amazon, LeanPub, and iTunes!

The book is 400 pages long, just shy of 80,000 words, and was a huge effort. It's such a relief to finally have it 'out the door', though publishing-as-I-write has been a great experience. Pre-first-edition, I've already sold over 2,200 copies of Ansible for DevOps on LeanPub!

Here are a few blog posts from Server Check.in where I describe more of the publication process:

I've published the first portion of a book I've been writing, Ansible for DevOps. This is my first-ever book, and I've written a little about the process of writing on Server Check.in's blog: Self-publishing my first technical book on LeanPub.

I'm excited about the early feedback I've already received—and I haven't even finished writing half the book! I'm hoping to finish the first complete draft of the book (and continue publishing it in stages on LeanPub) by summer 2014.

I recently told my Facebook friends that I was thinking of writing a book to help people get better photos with their fancy cameras, and received a lot of positive feedback.

Getting consistently sharp, vivid, interesting photos doesn't have to be hard.

Some of the things I want to write about include:

• Getting photos that aren't too bright or too dark.
• Getting photos where people aren't blurry.
• Making people look great.
• Taking pictures that are beautiful, more often.

I don't want to be technical in this book, other than introducing people, slowly, to important concepts in photography. I want to show people through example and experience exactly what's going on when they snap a picture that they later find to be ugly, horrible, or too blurry or bright/dark to use.

This month, my old Mac story about a IIci was featured on on the excellent Apple-related blog 512 Pixels, by Stephen Hackett: Old Mac of the Month: Macintosh IIci.

I briefly mention the IIci in my (not-yet-complete) Computing History article here on Life is a Prayer.com. I really liked the IIci, and it's probably one of my favorite Macs of all time, especially considering I probably owned and used it the longest!

Special thanks to my brother and dad, who not only helped me get into electronics and computing, but also helped me edit the article.