For 1 April: #mwlSecretBook reveal!

So, I wrote a book. And I didn’t tell people what it is.

The book is now out. You can buy it.

And it has an authentic, legit blurb from Ken Thompson, co-creator of Unix.

Explaining why I did it this way takes a little bit of context.

First:

People have sent me all kinds of guesses for the book topic. Some of you have guessed correctly. I haven’t told anyone that they’re correct, though. You people are perfectly capable of launching a dictionary attack on me, so the only answer I could give is “no.”

Mind you, some of those “nos” have been carefully phrased so that you’d interpret them as a “no,” when really they’re a “maaaaybe” or even a “yes, but I’m not going to admit it.” If someone guessed correctly I used answers like “I wish,” the unspoken second half is “and I’m self-publishing, so I have the power to make my wishes come true.” Or perhaps “I long to one day be sufficiently knowledgeable to write this book.” Technically accurate but certainly misleading statements.

I’m prepared to hide wildly behind those technicalities.

Second:

I’ve thought for a while that there’s space in the market for even smaller books than my usual Mastery titles. This is a test run of producing such a book. It’s half the size of my sudo, Tarsnap, and DNSSEC books for a reason. It’s also less expensive.

Third:

As I was writing up my 2017 year-end review I realized that the next book I wrote would be the 13th Mastery book. 13 is my lucky number, because what other number could be? I’d like to write four tech books this year, so that’s one every three months.

Looking at the calendar, I realized that quarterly releases would put me at April First.

Could I write and release the 13th Mastery book as an April Fool’s prank?

Except have it not be a prank? Have it be a serious tech book, on a real program, that solves actual problems in the real world?

Maybe.

Maybe I could. Three months for writing, tech review, copyedit, and production is danged aggressive, but it should be doable. And nothing concentrates my mind like an unbreakable deadline and the looming possibility of public humiliation.

I warned the sponsors. Dozens of you sponsored anyway. I’m torn between apologizing and posting an “I told you so” GIF.

Fourth:

Every so often, I get a cluster of emails complaining about my using both male and female third person pronouns in my tech books. Either women don’t belong in tech, or shouldn’t be in tech. A few offer arguments that “he” is gender-neutral in English. All of these emails include misogynistic statements of one form or another.

These emails arrive in groups. I hear nothing for months, and then four or five appear in the space of twenty-four hours. I suspect that my work comes up on some MRA message board or IRC channel and a few of the people hanging out there decide to present their case.

Overwhelmingly, these messages display the combination of sloppy logic and total lack of understanding of human nature that seems to be a hallmark of a certain fringe of techies. Indeed, they show a failure to understand what it means to be human, or what it means to live in a liberal society.

I delete these messages as soon as I realize what they’re about. Most often, I don’t make it past the first paragraph. (Many times the email is thousands of words in a single paragraph, and I wouldn’t finish reading that anyway.) I do offer an answer in my blog, but this project game me an opportunity to respond more… usefully.

So, for the record: I mix male and female pronouns for a reason. Women are a thing.

I also use the singular they. It’s been valid since Shakespeare’s day, and it’s a pronoun for some people. If you think the singular they is ruining our language, you’re wrong; English was ruined long before you or I got here. (It’s fine for you to not like that pronoun, but that’s your taste. I write my books to my taste. My taste includes the panoramic, painful panoply of our abominable tongue.)

If we had different pronouns for different races, I’d use them.

If we had different pronouns for different faiths, I’d use them too.

Tech is a diverse field and needs to become more diverse. Doing otherwise is disrespectful, dehumanizing, and a shameful waste of human potential. (Go read your Adam Smith, and not just the libertarian-friendly bits about the awesomeness of the free market.)

Everyone deserves to see themselves reflected in books. When writing fiction I work to make my female characters just as utterly screwed-up or as completely pig-headed and smart as my male characters. I can’t imagine doing otherwise in nonfiction.

Does this make me a feminist? To the people who write these emails, certainly. But a proper feminist would hear me saying “women are a thing” and tell me that “women are not things.” Like “firewall,” I’m not sure what the word “feminist” means today. I want to see female schmucks promoted just as quickly as male schmucks. I want everybody, including women, to no longer need to fear verbal or physical assault. If that’s your definition of feminist, fine, slap it on me. I’m gonna keep doing my thing.

Fifth:

Writing is a business.

I’m a businessman.

And if there’s a market, I should serve it.

#mwlSecretBook comes in two editions. They’re differentiated by third person singular pronouns. Any third person singular pronouns that appear in the standard edition, for normal people, are feminine. Any third person singular pronouns in the special “Manly McManface” edition are masculine. That’s a much smaller market, however, so the Manly McManface edition is much more expensive, because economics.

(Remember, book 13. 1 April. When else could I do this?)

Sixth:

Soroptimist International of Grosse Pointe does a lot of work in the Detroit area. They raise money for women’s scholarships. They fight human trafficking. They support domestic violence shelters that help hundreds of women a year. My wife is a member. These ladies work damn hard.

For each copy of the Manly McManface edition sold, print or ebook, I will donate one dollar to SIGP.

Should you buy that expensive edition to make me donate money? Nah. It’s more effective for you to donate directly. You should only buy that edition if you’re too weak to tolerate women existing in your life.

Seventh:

Presented for your consideration, at long last: (drum roll) (more drum roll) (eye roll) (blare of trumpets) #mwlSecretBook! (fireworks) (children’s chorus) (shrieks of disappointment)

It’s available in ebook as I publish this blog post. Print will be coming in the next couple of days.

PS: I moderate comments with a heavy hand. If you’re offended that I created a book just for you, chances are I’ll either delete your comment or mock you.

On Sponsor Gifts

(Posted so I can refer to it later.)

Last week, Liz and I converted this:

into this:

Note the little stack of customs forms off to the side. It’s like I’ve learned a lesson from standing at the post office counter filling out those stupid forms. Sponsors should get their books soon.

This seems like an apropos moment to talk about what I do for print sponsors. I say I send them “a gift,” but what does that really mean? The obvious thing to ship them is a copy of the book I’ve written. Flat-out selling print books online has tax implications, though.

Sponsors might have guessed that they’d get a copy of the book. But I shipped them the hardcover, which isn’t my usual practice.

That’s because I send sponsors a gift. As it’s a gift, I get to choose what I send. I want to send them something nice, to encourage them to sponsor another book. It makes no sense for me to send a sponsor a Singing Wedgie-O-Gram. (Well, maybe a couple sponsors. You know who you are.)

The poor bastards who bought into my scam–er, sponsored my untitled book–have no idea what’s coming. As of right now, their sensible guesses are woefully incomplete.

Future books? They might get a copy of the book. They might get book plus something. They might just get the something. Folks who sponsor the jails book might get a cake with a file in it. Who knows?

It’s a gift. It’s my job to make that gift worthwhile.

And to amuse myself. Because otherwise, what’s the point?

“SSH Mastery, 2nd ed” in hardcover

I’ve been publishing books for about a quarter century now. At long last, one of my books is out in hardcover. With a dust jacket and everything. Introducing the newest version of SSH Mastery.

Why produce this book in hardcover?

First, because I need to know how to do it. Self-pub hardcover books are a different beast than paperbacks. One day I’ll have a serious need for hardcovers. That’s not the time to learn how to create them. I’ll need those skills in advance.

And second, because I wanted to. Because how cool is this?

Hardcovers are not cheap. This book retails for $39.99. Much like paperback print on demand, I expect the price to drop with time.

In theory, the hardcover will withstand more abuse than a paperback. I love theories. They make spending forty bucks on a book you can get for ten in ebook sound sensible.

I’ve ordered a case of hardbacks, as gifts for the fine folks who sponsored this book.

Also, this book uses my own ISBN, 978-1-64235-022-7. As I have very few combination book nerd/tech nerd readers, let me explain the joke: this is ISBN 22 out of my block of 1000, 978-1-64235-022-7. You have my permission to roll your eyes now.

As I don’t expect anyone to actually purchase the hardcover edition, I let myself have fun with it. The dust jacket is very BOFH, and contains Extra Rat.

speaking at mug.org 10 April 2018

On 10 April 2018, I’ll be giving speaking at mug.org. Each MUG meeting has two presentations, one long and one short. Somehow, they’ve given me both of them.

My first, longer talk will be on ZFS, including some newer developments.

The second talk? I’m not saying.

The MUG talks coordinator, JM, agreed to let me present on the topic of my next book, the one with the undisclosed topic, without knowing what that topic is.

This gives me a hard deadline; either I’m in a position to announce the book by then, or the project fails. But hey. No pressure.

So, if you want to know the topic of #mwlSecretBook, show up at mug.org on 10 April.

In unrelated news, MUG is a great group that can always use volunteers. For example, I suspect they might desperately need a new talks coordinator on 11 April…

SSH Mastery 2/e out

For the last week or so, the new edition of SSH Mastery has been leaking out.

It’s now available in print via Amazon, and in ebooks just about everywhere: iTunes, Kobo, my bookstore, and more.

The print version will soon be available through Ingram’s distribution as well, including a dust-jacketed hardcover version. That’s going to be a couple more weeks, though.

Sponsoring a Scam

I’m writing a multi-Unix technology book that doesn’t have a title yet.

Well, okay, it has a title. But I’m not saying what it is. The reasons why will be obvious once the book comes out. It’ll be out before May.

#MWLSecretBook will be fairly short, about 15,000 words–about half the size of Sudo Mastery. A tech book novella, as it were. As such, it will be less expensive than other Mastery books.

When you find out what this book is, you’ll probably groan and roll your eyes. Or send hate mail. Or wonder why it hasn’t existed until now, when the need is so obvious and a whole bunch of you don’t know the topic at all.

I did a Twitter poll asking if I should offer sponsorships. The reaction was widely split between “no, you’re an idiot,” and “yes, you’re a maniac.”

I have mixed feelings on offering sponsorships because, well, this really is a pig in a poke. I’ve decided to go ahead, because a) I could use the money, and b) the sponsorships include pretty clear warnings. So:

MWLSecretBook – print sponsor
MWLSecretBook – ebook sponsor

The image is a narrow piece of the cover art.

This whole thing is a complete rip-off. I mean, PT Barnum would approve. That’s why the rates are at my usual tech book sponsorship rates, because if you want in on a scam you want all in.

And let me say in advance: I’m sorry.

“SSH Mastery 2/e” copyedits back

My copyeditor returned the corrected manuscript for “SSH Mastery, 2nd Edition” to me last night. You should be able to buy the book within a few weeks.

In unrelated news, the first draft of #mwlSecretBook is coming along nicely. It’ll be the shortest Mastery book I’ve ever written, but at some horrific moment in your professional career you’ll be desperately glad to have it.

Podcast Interview with Yours Truly

Season 2 Episode 7 of Chris Sanders‘ Source Code podcast features me. It’s a tech podcast, yes, but as Chris and I are both writers, we talk writing. Plus growing up in a farm town, reading, and the assorted unspeakable horrors of the literary life.

Chris not only donates his book royalties to the Rural Technology Fund, when he interviews someone on his podcast he donates $100 to a charity of the guest’s choice. I chose the Soroptomists International of Grosse Pointe, who are doing good boots-on-the-ground work on Detroit’s human trafficking problems. They’re less the “Ladies Who Lunch” and more the “Ladies Who Launch.”

The bad news is we, of course, discussed Savaged by Systemd. Somehow, we kept the podcast’s PG rating.

My ConFusion Schedule

I’m girding my loins, gritting my teeth, and leaving the house this weekend. Specifically, I’ll be attending ConFusion, one of Detroit’s major F&SF cons. If you’re attending and want to avoid me, here’s a few panels and events I’ll be participating in.

11am Saturday – Petoskey – Last Exit Before The Worst Timeline
12pm Saturday – Isle Royale – The Ancient 1980s
5pm Saturday – St Clair – Mass Book Signing

You can roam the con freely those three hours. Otherwise, keep your eyes open and be ready to dodge away.

MWL’s 2017 Wrap-Up

It’s that time again. Time to reflect on my myriad personal failures in 2017.

The obvious place to start is my 2016 wrap-up post, where I listed goals for 2017. As usual, these goals were wildly delusional.

The short answer is, my iron was back up to normal. My writing speed wasn’t, though. I’d lost too much general health, and needed hard exercise to recover it. Yes, writing requires physical endurance. Maintaining that level of concentration for several hours a day demands a certain level of blood flow to the brain. I could have faked it in a day job, but when self-employed as an artist? Not so much.

Then there’s travel. I did my usual BSDCan trip, plus two educational trips to Lincoln City, Oregon. The current political mayhem convinced me that if I wanted to hit EuroBSDCon any time in the next few years, I should do it in the very near future. So I went to Paris, where I promptly got pickpocketed. (Thankfully, they didn’t get my passport.) I was actively writing the third edition of Absolute FreeBSD, so I visited BSDCam in Cambridge to get the latest information and a sense of where FreeBSD was going. I also did weekends at Kansas LinuxFest (because they asked and paid for my trip) and Penguicon.

(Because people will ask: why EuroBSDCon and not AsiaBSDCon? A six-hour transatlantic flight requires that I take a substantial dose of heavy-grade tranquilizers. I’m incapable of making intelligent decisions while on those drugs, or for several hours afterward. They don’t last long enough for twelve-hour flight to Japan, so I need to be accompanied by someone qualified to tell me when I need to take the next dose partway through the flight. This isn’t a predetermined time that I can set an alarm for; it depends on how the clonazepam affects me at those altitudes. A drug overdose while flying over the North Pole would be bad. When I can arrange that qualified companion, I’ll make the trip.)

I need most of the preceding week to prepare for long trips. I need the following week to recover from time shifts and general exhaustion. Additionally, I have to hoard people juice for a few weeks beforehand so I can deal with folks during these expeditions. Travel disrupts my dojo time as well, which impacts my health.

Taken as a whole: I didn’t get nearly as much done as I hoped.

Here’s my complete output of big books.

Or, everything I put out: one novel, one tech book, one story, and one novella.

I wrote more stories, but Kris Rusch bludgeoned me into submitting them to trad markets. (The woman is a brute, I tell you. Cross her at your peril.)

Among my 2017 titles, my fiction outsold the tech books. No, not Prohibition Orcs–all four of the people who buy those love them, but the sales tell me I’ve done something wrong with those tales.

My cozy mystery git commit murder outsold Relayd and Httpd Mastery.

But what outdid them both, as well as most of my older books? What title utterly dominated my sales for the last quarter of the year? It was of course, my open source software political satire disguised as porn Savaged by Systemd: an Erotic Unix Encounter.

I can’t believe I just wrote that paragraph.

The good news is, once I recovered from EuroBSDCon, my writing got better.

I finished Absolute FreeBSD, 3rd edition and submitted it to the publisher.

I wrote the second edition of SSH Mastery (no link, because you can’t order it yet.)

I’m plowing through git sync murder, the sequel to git commit murder. I don’t get to see the new Star Wars movie until I finish GSM, so hopefully that’ll be this month.

All in all, I wrote 480,200 words in 2017. Most of that was after September. It’s annoyingly close to breaking half a million, but after 2016’s scandalous 195,700, I’ll take it.

One of the nice things about being an author is that most of your income is passive. You do the work, and the money trickles in for years afterwards. I had money coming in while I was out of commission. The bad news is, that income slowly drops. If I’m to stay an author instead of becoming a wage peasant, I have to schlep some books out PDQ. I can do it, provided I remain focused on production.

That slump is the big reason why I broke down and started a Patreon. It’s why I started taking sponsorships for tech books. You folks carried me through my health problems. I can’t thank you enough.

The fact that AF3e is trad published complicates the financial picture. I won’t see any money from that book until 2019. No, I’m not complaining–that’s just a fact of life, and I knew that going in. But it provides extra motivation for getting my butt in gear right off in 2018.

So 2018 will be my Year Of Making Words. The finest words, of course. Artisinal. Straight from Detroit, a third world city in America’s heartland.

So what’s on tap for 2018? What’s the plan?

  • BSDCan, Penguicon, and two educational trips to Lincoln City, Oregon. That’s it. Under no circumstances will I leave North America, sorry.
  • write 600,000 words, or 50,000 words a month.
  • Complete and release four tech books
    • SSH Mastery 2nd ed
    • FreeBSD Mastery: Jails (I suspect this will turn into two books, it’s a huge topic)
    • either Mastodon Mastery or Ansible for Legacy Systems.
    • #MWLSecretBook, which I can’t talk about until for now, for reasons which will become clear once the book comes out
  • Write the tech book I didn’t complete above, and release it if there’s time
  • Write four novels
    • git sync murder, a sequel to git commit murder
    • Bones Like Water, or Immortal Clay #3
    • Drinking Heavy Water, Montague Portal #5 or Aidan Redding #4
    • To Be Decided From a List of Candidates, All of Which I Really Want to Write
  • Be sufficiently flexible to kick Ray Percival in the head at BSDCan. A front kick will do, but I’m shooting for the high-flexibility side kick as a stretch goal.
  • Exercise enough to drop twenty pounds
  • Stay married while doing all of the above
  • Stay alive

Other than the last two, these are all deliberately fail-forward goals. If I only get three tech books done instead of four–hey, I’m ahead by three tech books! If I only drop ten pounds, that’s better than gaining ten. “Stay married” and “stay alive” aren’t fail-forward goals, but I have a good idea how to achieve them both.

This time next year, come back to see exactly how I failed!