MS Word auto-recovery files and Dictation

Today, I learned about Microsoft Word auto-recovery files.

If Microsoft Word crashes and can’t auto-recover the document, find the autosave file. The location is given in File->Options->Save. Sort the directory by date, and your autosave should be at or near the top. The file name ends in .asd. Copy that file elsewhere and open it in Wordpad.

Your text will be therein, stripped of all formatting but present.

In related news: I’m trying dictation. I know several authors who produce several thousand words per hour with dictation. I would like to produce several thousand words per hour.

Seemingly unrelated fact: I habitually hit the “save” button after typing every sentence. Note the key word: typing.

In more related news: installing Dragon 15 has made Microsoft Word lock up three times today. The third time, it couldn’t auto-recover the lost text.

And I hadn’t even thought about saving. Because I automatically hit “save” every sentence.

Beware your habits. They will cause you pain when you change.

Also: computers are terrible. I need a stenographer. Who understands MS Word styles.

“SSH Mastery, 2nd Ed” News, Sponsorships, and Cover

SSH Mastery has been my best-selling title since I published it in 2012.

SSH Mastery has been on a five year mission to find and eradicate passwords. SSH has changed in the last five years. SSHv1 is no more, except where it is. A whole bunch of crypto algorithms are no longer in use, except when they are. We get jump hosts and centralized key management, except when we don’t.

It’s time for it to return to dock and get a refit. The new one will be cleaner! Brighter! Cover certificates! Capable of reaching Warp 5–no, wait, wrong story, never mind. But the cover will be pretty sweet. Here’s a rough draft.

I present to you: the Bloata Lisa!

SSH Mastery, 2nd Edition should be out before BSDCan 2018. If I do everything right, I’ll have two new tech books for folks in Ottawa.

This time, I’m soliciting print sponsors and ebook sponsors. As this is my best-selling Mastery book, I’ve raised the sponsorship prices a touch. Sponsors can expect readers to gloss over their names for years to come!

I must also concede that I’m hoping the sponsorships will help offset buying a block of ISBNs. I need ISBNs to produce the hardcover dust-covered sewn-spine print edition.

Oh, wait–did I not mention that? Sorry. Yes, hardcover. Stitched pages, not glued. A cloth cover and gold-stamped title beneath a glossy dust jacket.

Hardcovers are a little tricky, so I’m not promising I can accomplish that. Other authors manage it, though, so I’m not carving a new tunnel out of a mountain here.

A book needs 3-5 ISBNs, depending on the printing facilities I choose. As a US citizen I can buy 1 ISBN for $125, 10 for $295, 100 for $575, or 1000 for $1500. 100 ISBNs will last me for 20 books, but I know dang well that if I buy 100 I will regret it. The price of these arbitrary reference numbers will only increase, though, and I can easily see running out in a few years. So: I’m getting 1,000. For $1500. Ouch.

But hardcovers.

ISBNs will also let me take advantage of print-on-demand facilities in Europe, Australia, and post-Brexit UK. I’ll be able to fulfill wholesales orders for my books. It’s a reasonable business investment.

Leveling Up

For those who can’t be bothered with long posts, here’s the short version:

My novel Immortal Clay is now featured as part of Kris Rusch’s Fear Bundle on Storybundle, one of the major book bundling sites. You can grab my novel, as well as thrilling and scary books from authors like Dean Wesley Smith, Leah Cutter, Rebecca Senese, Gary Jonas, Mark Leslie, Sean Costello, J. F. Penn, and Kristine Katherine Rusch.

If this was all that was going on, it’d rate a blog post. Storybundle is a big step up for me. I’m proud to be there. But this tale’s a little more complicated.

Immortal Clay is what writers call “a book of the heart.” Even as a child, pod people fascinated me. The Body Snatchers are Invading? I’m there. Carpenter’s The Thing is a favorite film. Philip K Dick’s tales of things that look human, that think they are human, but aren’t, have been my literary comfort food for decades.

In 1995, I realized that these tales all had one thing in common: they didn’t go far enough. The lightning strikes of implications and possibilities drove me to fill entire notebooks in an effort to get that inspiration to stop ricocheting around inside my skull.

And I lacked the writing skill to do anything with them. I tried, but… no. I just wasn’t good enough. So I wrote other novels, trying to develop the ability to express that manic inspiration.

Time passed.

I kept writing. Kept practicing. I love stories, I love storytelling, and I was going to master this skill.

I wrote in a bunch of different genres, sent out submissions to different short fiction markets, and collected the obligatory ticker tape parade of rejection slips. My favorite genres to read are SF and mystery/thriller, but what initial success I had came in horror.

Apparently I was a horror writer.

I focused my fiction writing time on horror, without much more success. Every day I polished my technique, obsessed with perfecting my storytelling.

Meanwhile, my nonfiction career writing about Internet technology exploded. Internet tech meshes perfectly with horror, by the way.

But then my fiction career stalled. After that initial small success, nothing happened for years.

I kept learning. And seeking teachers.

I’m selective on teachers. I want a mentor who has, say, won multiple awards over a course of multiple books. Or a working writer who’s consistently published many books, over decades, through a variety of channels. And in either case, they need to be a good teacher. Despite the old saying, not everyone who can do can teach.

Kris Rusch is one of the few authors who’s published literally hundreds of books and who teaches the craft of writing.

My first course with her was challenging–not because of the lunatic pace, or the jetlag, or being away from home for ten whole freaking days when I’ve successfully arranged my life so that I only need pants for the grocery store and the dojo. No, the hard part was how she methodically, kindly, and mercilessly blasted down my mental barriers. She has a rare talent of adjusting the lessons to the students. The lesson I needed involved dynamite. The second day, she called for someone to bring a bucket and a mop, because my brain had exploded out the back of my head.

I’m sheepishly proud that I was the last straw that finally drove her to write a book about how writers mess themselves up. (I’m in that book, anonymously. The truth is far uglier than what she wrote.)

During an afternoon break in the middle of the week, she asked me to stay behind. I knew what was coming. Obviously, she didn’t want to flunk me out in front of the class. It would be best for everyone if I just quietly slunk away before anyone came back from the bathroom and the snack table. After all, who wants a big messy scene?

Instead, she told me I could write fiction. That I could do it well. And she said something I never expected to hear: “Do you know you’re a science fiction writer? Has anyone ever told you that?”

No. Nobody ever told me that. I had a stack of rejection letters that said I wasn’t.

But Kris is not a person who sugarcoats the truth. That week, I watched her politely and helpfully feed people all sorts of bitter medicine–always with encouragement, yes, but a bunch of folks got sent back to the basics of the craft.

After that class, I went home and slept for three days. When I woke up, I waded through the wreckage of my mental barriers and started writing Immortal Clay.

Immortal Clay is science fiction, straight from the Pod People Playbook. It’s got a lot of horrific elements in it–it starts with the extinction of the human race, and goes downhill from there. People tell me it’s about hope and what it means to be human, but I’m pretty sure it’s about horrible monsters, small town secrets, and the importance of flamethrowers.

It’s horror by an SF writer–or SF by a horror writer. Something like that.

Starting this series felt I’d finally let out a breath I’d been holding for twenty years.

And of all the books I’ve written, it’s the one that generated the most demands for a sequel. The first pleas for book 3 arrived the morning after Kipuka Blues appeared. (Bones like Water will escape in 2018.)

And now, my teacher curated a Storybundle.

She asked for the book of my heart.

And the Fear Bundle is stuffed full of books written by folks who bled just as much to learn their art, and put just as much of their own hearts on the page. Seriously, I’m just stunned at the names I’ve been packaged with. The authors I haven’t read? I’ll be reading every one of them, just based on the company they’re keeping.

You really want this one.

I have a Patreon now

I’ve done it. I’ve sold out. I’ve joined the trendy hip crowd.

By popular demand, I now have a Patreon.

Why announce this now? Well, I’ve finished the intensive work on the third edition of Absolute FreeBSD. I won’t have the rights to distribute electronic versions of AF3e to patrons. (Why? Remember, authors don’t sell books; they license copyright. I’ve licensed those rights to No Starch Press.) I will have the rights to distribute all of the Tilted Windmill Press ebooks, though. I feel it’s wrong to ask people to patronize me for working on stuff I couldn’t share with them.

Stupid ethics.

Financially, your best choice is to look at the books I write as they come out and purchase the ones you want. And I am perfectly good with that choice. I’m perfectly good with people who never read my stuff at all. My Patreon is for people who want to offer ongoing support, and get a couple tidbits in the bargain.

If you want to throw me a couple bucks but don’t Patreon? I have a tip jar. Or buy another book.

Short on cash? Reviews at the ebookstore where you bought a book are always nice.

Utterly indifferent to my existence? Then why did you read this blog post all the way to the end?

New story: Savaged by Systemd

Yesterday, I put a short story up as an ebook. This was a wild experiment that I wrote on a whim.

When I say “wild experiment,” I don’t mean I decided to play with tenses and point of view. No, I decided to spend one day writing a lunatic piece, something that I’ve never written before.

Erotica. Sort of.

Computer erotica, to be specific.

Linux sysadmin erotica, to be more specific.

OK, fine. Systemd erotica.

It’s called Savaged by Systemd. And while it certainly contains erotic content, it’s got a bunch of other things in it too.

I try to wait to announce these things until they’re available in both print and ebook. But some weird things happened.

Here’s last night’s Amazon “hot new erotica releases.”

#2? This is madness.

Hot new releases only include titles released in the last little while. It doesn’t mean much compared to the general “books that are best-selling right now” list. So here’s a screenshot of Amazon’s erotica best-sellers from last night.

I’m #15. This, also, is madness.

But this book involves technical topics. It’s also showing up in the Unix category. Here’s a screenshot of Amazon.ca’s Unix Hot New Best-Sellers.

Hitting #1 in the Hot New Unix Books category is no big deal for me.

This morning’s SF Erotica best-seller list?

Strangest of all?

Here’s my Amazon ebook sales dashboard for the last three months, displaying unit sales.

Those little yellow marks all along the bottom? That’s my living. I’m not complaining about it. I get a reasonable middle-class wage compared to non-tech workers. Don’t get me wrong–if you offer me money I’ll take it. Reader donations in the form of book sponsorships have helped me out in desperate times.

And Savaged by Systemd is only $2.99, so I don’t make nearly as much off of one of those as I do a tech book.

But still: that’s a mighty pretty looking set of spikes, over there on the right hand side.

And it’s getting reviews. Goodreads is famous for giving lower reviews than most other book sites. Not only is SbS getting all five-star reviews there, it’s getting long and detailed reviews.

One of those reviews captures what I was trying to do.

Writers are pretty good about hanging on in the face of adversity. We’re accustomed to the larger world pretty much ignoring our feeble efforts.

Success disorients us.

My social media accounts are flooded. My email is worse than ever. Everybody on LinkedIn suddenly wants a piece of me. (I only LinkedIn with people I’ve actually worked with, btw.)

Despite the heady rush of literary success, I need to make some words. The deadline for the new Absolute FreeBSD is pretty inflexible, if I want it in print for BSDCan.

AF3e status, 22 August 2017

Your irregular “Absolute FreeBSD” status report!

It’s at 123,700 words. 12 of 26 chapters exist as first drafts. (Yes, the last report said 7 of 24. I can’t count.) Two more chapters are partially done. One of those partially-done chapters, on “Pre-Install Considerations,” won’t be done until I finish the whole book. I keep going back to add tidbits to it. It’s complete, except when I find something else I have to add to it.

The current status looks like this. Chapter titles subject to change. Again, the ideal chapter length of a No Starch book is about 5000 words. The really long chapters have no obvious breaking point, so I’m kind of stuck.

0 – Introduction (7500 words, sent to NSP)
1 – Getting More Help
2 – Pre-Install Considerations (4900 words)
3 – Installing (write last, because screenshots are evil)
4 – Booting (11,400 words, sent to NSP)
5 – Backups
6 – Kernel
7 – Networking (8800 words, sent to NSP)
8 – Configuring Ethernet (8500 words, sent to NSP)
9 – Security
10 – Partitioning & GEOM (10700 words, sent to NSP)
11 – UFS (9000 words, sent to NSP)
12 – ZFS (8000 words, sent to NSP)
13 – Other Filesystems (11,700 words, out for review)
14 – More Security
15 – /etc
16 – Packages (8600 words, NSP tech review done)
17 – Ports (6800 words, NSP tech review done)
18 – Advanced Software Management (7400 words, in process)
19 – Upgrading
20 – Small System Services
21 – Performance and Monitoring (14,000 words, out for review)
22 – Jails (6100 words, sent to NSP)
23 – Misc Crap
24 – Panics & Bugs
Afterword

See the prior status report on why I’m writing in this order.

Progress is slower than I’d like, thanks to my trip to England for BSDCam. (Jet lag and travel kills tech writing.) But BSDCam changed the content of this book to your benefit. But I have a few more weeks until EuroBSDCon, so I’m grinding out as many chapters as quickly as I can without sacrificing quality.

I suffer for FreeBSD, so you don’t have to.

The real challenge here has been my fiction projects. I’ve been working on a new Beaks novel, but it’s just not working. I tried switching to the third Immortal Clay book, but those words just won’t come.

And by “won’t come,” I mean I’m producing about 700 words an hour. And I’m actually relieved when my 90 minutes of fiction writing time ends. That’s bad. It’s stressing me out.

Both IC and Beaks are kind of dark. And right now, it seems that my brain doesn’t want dark. Part of that is the world, and part of that is my serious effort to get AF3e finished in time for BSDCan 2018.

On a whim, I started working on the next Montague Portal novel. Montague Portal is light and escapist. Yes, there’s murders and stabbings and stuff, but they’re fun murders and stabbings. My subconscious sighed with relief and started spitting out 1200 words an hour from a cold start.

So, it looks like “Drinking Heavy Water” will be my next novel.

More updates as events warrant.

BSDCam Trip Report

The FreeBSD Foundation has posted my BSDCam trip report. I also want to sincerely thank the Foundation for helping defray my expenses.

Robert Watson runs an excellent event. And what I learned at BSDCam will appear through the new Absolute FreeBSD.

Speaking of which, I need to go make some words. Bye.

Contributing to FreeBSD

I’ve talked to a whole bunch of folks who say things like “I’m a junior programmer. I’m looking for a way to help. I have no specific expertise, but I’m willing to learn.” Today, I present such junior programmers with an opportunity. An opportunity for you to learn skills that will be incredibly valuable to your career, and will simultaneously expand your career opportunities.

I’m at the FreeBSD BSDCam devsummit, gathering dirt information for the new Absolute FreeBSD. One of the topics is testing.

For decades, FreeBSD has relied on its users for testing. They expect users to install pre-release versions of the OS and exercise them to identify regressions. That’s necessary, but it’s nowhere near enough.

The FreeBSD Testing Project is building an automated test suite for the entire operating system. They have a whole mess of work to do. There’s only four people on the team, so each additional person that contributes can have a serious impact. They have tutorials on how to write tests, and sample tests.

There’s a whole bunch of tests left to be written. You have an almost open field. They need tests for everything from ls(1) to bhyve. (Yes, ls(1) broke at one point in the last few years.) Everything needs testing. Learning to write, submit, and commit small tests is valuable experience for developing the big tests.

And “I perform automated testing of my own code before the test team gets to see it” is a valuable item on your resume.

What’s more, learning to write tests for a system means learning the system. Developing tests will transform you into a FreeBSD expert. Once you’ve demonstrated your competence, worth, and ability to work within the project, other FreeBSD teams will solicit your help and advice. The Project will suck you in.

Testing is perhaps the most valuable contribution anyone can make to an open source project. And this door into the FreeBSD Project is standing wide, wide open.