Why was #pamMastery so hard to write?

https://io.mwl.io/@quotebot/113374604852149697

I sold 17 hardcovers of "PAM Mastery" in the US in February. No idea who or where or why.

Trying to reverse-engineer sales reports can drive you daft. I will never know how this happened, but must be content with the knowledge that someone has a #PAMMastery Book Fort.

Did my monthly check on Amazon book reviews. Top of the list for each name?

A one-star on #savagedbysystemd because they totally missed the joke and didn't read the description.

A three-star on #pammastery because it didn't contain what they wanted, only what was in the book description.

Welcome to being a writer. People judge your work based on what they want, not what it is. Here's your boot to the head, get back to the keyboard. ​

Okay, enough whinging. Back to the keyboard.

Pondering classic art to parody for the #sudomastery cover. Preferably something where I can get both Beastie and Tux in.

I doubt I can top the #pamMastery cover, but gonna try.

The official final pic of my 2018 releases and anthology appearances.  

Not shown: the #pammastery and #relaydmastery hardcover reissues.

Once you know how to do hard cover books, they take about two hours. Here's #pamMastery

(  link until image problems are fixed on bsd.network: https://twitter.com/mwlauthor/status/1047468346738966528 )

Then it's two weeks for the print proof to arrive, ten seconds to see the obvious typo, and fifteen minutes to fix it. #headdesk

so KDP accepted #pamMastery and #relaydMastery under new ISBNs. Not a bad day's work.

#fmse is my current bugaboo, though.

Going through #pamMastery eproof, and feel compelled to post this tidbit:

"To make an SGI sysadmin scream and gibber, say "Hey, remember IRIX's two incompatible PAM stacks? Good times!"