New Cocktail: The Afterlife

The other night I was privileged to drop in to Barnes & Noble to a book signing by a former student, Blue Cole.

Blue, who is actually the son of a high school classmate, was one of those charming, good-looking teenagers who you feared might amount to nothing.  Dimples and blue eyes will only get you so far, after all.

However, Blue has grown up to be a fine upstanding citizen who is only a little worrisome when his wife takes him to big box stores and leaves him unattended.  This novel, Evil Upriver, is Blue’s third, unless I’ve lost count.

But Dale, I hear you musing, supernatural horror is not your thing.  You even write about it in the chapter on AUDIENCE in your own upcoming book, Lichtenbergianism: procrastination as a creative strategy.  Indeed it is not, but 1) I go to book signings for all former students; and 2) Blue personally invited me to come and asked me to wear my pearl earring, since that’s what the bartender named Lyles in the book wears.

How could I not invent a cocktail and take him a small box with said cocktail and other mini-bar accoutrements?

Actually, I was going to bring him the Smoky Topaz, which should be good enough for any normal purpose, but then my Lovely First Wife suggested that I invent a cocktail called The Afterlife because reasons.

It was a rush job, but I did it:

The Afterlife

  • 1.5 oz bourbon
  • .75 oz Amaro Angostura
  • .25 oz Ancho Reyes Liqueur
  • dash 18•21 Havana & Hide Bitters

The idea was that it would be at first taste an interesting take on the Manhattan with a somewhat toasty finish (GET IT, KENNETH?), but however, and also too, I felt it was lacking.

So tonight, I futzed with it and now it’s pretty solid:

The Afterlife, redux

  • 1.5 oz bourbon
  • .75 oz Amaro Angostura
  • .25 oz Ancho Reyes Liqueur
  • .25 oz simple syrup
  • .25 oz 18•21 Blackberry Peppercorn Shrub
  • dash 18•21 Havana & Hide Bitters

Stir with ice, strain, serve on the rocks with an orange peel.

Rather more ingredients than I normally prefer, but it’s tasty. Quite tasty.

(Sorry, Blue, about the recipe I gave you last night.  Feel free to use it, but this is the recipe that will appear in my second book.)

The book

Yes, it’s true, I have written a book.

The title is Lichtenbergianism: procrastination as a creative strategy, and yes I have a macro that types that out for me.  I was a little startled a couple of weeks ago when I started checking the blank spots in the text I needed to fill in and found that there were none.  I was, in essence, done.

Why haven’t you heard about this?  You have if you also read my other blog, Lichtenbergianism.com, where I have tended to shunt all my whining about creative work.  Even there, though, I haven’t really documented the travails of the process.[1]  It’s more of a marketing/social media tie-in for the book, the sales of which of course I expect to catapult me into the first ranks of Twitter like Austin Kleon and others.  Too much whining is not customer-friendly.

So why can’t you give me money this very moment?  Several reasons, and here you get to read me whine because THIS IS MY BLOG, KENNETH.

√ 1. I invited my fellow Lichtenbergians to proof and kibbitz the text along with a select few others.  Their input has been valuable, so thank you, guys!

√ 2. That necessitated—as it should—corrections and emendations of the text, and I’m about done with that.  I have two or three more sticky notes on my monitor to do, and then it’s on to…

3. I have to export the text from Scrivener, the most excellent authoring tool from Literature & Latte.  (If you are writing anything of any length, go buy this software and before you do anything go through the entire tutorial.  Pro tip: after the third time you’re thinking there must be an easier way to accomplish something in the program, take the tutorial again.)

4. I have to edit that Word file, applying styles to paragraphs and terms so that I’ll have a slightly easier time of it when…

5. I import the text file into InDesign to lay out the book.  I expect this to be an orgy of moaning and whining.  I’ve done a little work already, but I’m not really happy about any of it.  For one thing, the font I thought I was using for the main text doesn’t really work for me, so I switched to a simply sans serif font, and now I can’t find a contrasting font for headings and quotes that I like.  Ugh.

5a. I have to go back and make sure that all the images I’m using are at least 300 dpi for publishing purposes.

6. I have to design the cover.  Again, I’ve done some work but hate all of it.  (My placeholder design, which I’ve used as an image in several posts, doesn’t even have my name on it.)

7. I have to export all of that above and send it to my estimable publisher, fellow Lichtenbergian Jeff Bishop at Boll Weevil Press, where he will publish it via our Lichtenbergian Press imprint.[2]

Then you can give me money.  Two weeks, maybe?

—————

[1] Aren’t you glad I didn’t write “haven’t logged my slog”?  You’re welcome.

[2] Jeff’s most recent book, Agatahi, is a marvel: the Cherokee Removal, aka The Trail of Tears, told via first-person accounts of the Cherokees themselves.  Go buy it.  It is profoundly moving.

There’s a rule for that

I’m at the beach, not doing any editing or design on my soon-to-be-published Lichtenbergianism: procrastination as a creative strategy, nor even on the placement map for Alchemy, just reading, doing crossword puzzles, and generally basking. The book I just finished is Jingo, one of Terry Pratchett‘s brilliant Discworld novels, and though it was written in 1997 its take on jingoism, war, and especially immigrant Others is disturbingly on point.

But that’s not why we’re here today.  This passage:

[The incompetent Lord Rust is speaking, about to lead his non-army into an epic Light Brigade blunder] “Glory awaits, gentlemen.  In the words of General Tacticus, let us take history by the scrotum.  Of course, he was not a very honorable fighter.”

…reminded me of a Bible verse.

Wait, where are you going?  I can explain myself.

The Talibaptists think gay people are squicky, and they will refer to Leviticus 18:22 and 20:13 as their prooftexts.  In return, otherwise sane people will refer to equally outdated prohibitions about shrimp and tattoos. Very occasionally, the wryer among us will throw in Deuteronomy 25:11–12.  You’re not familiar with that particular rule?

Here:

 If two men are fighting with each other—a man and his fellow Israelite—and the wife of one of them gets into the fight, trying to save her husband from his attacker and does so by reaching out and grabbing his genitals, you must cut off her hand. Show no mercy.

I mean to say, wot?  It’s as if Rule 34 applied to the Holy Book.

Before we get to my main point, let me say that I did a little reading of some explanations of this bizarre dictum and it actually does make a kind of sense in context. Elsewhere in Deuteronomy there are rules about a man whose testicles have been damaged no longer being able to enter the Temple, i.e., he’s no longer One of Us.  His entire family would suffer.  So a woman who did that to a man would have committed a truly serious crime.[1]

Often, when confronted with examples like this of outrageous Old Testament “laws,” the Talibaptists will wiggle and wriggle and contort themselves into pretzels to “explain” them away.  If you’ve ever had to listen to them, it provides good exercise for your eyebrows and pursed lips. Surprisingly, though, I found an exegesis that was sensible; it would be a miracle indeed if the Talibaptists threw their main weight behind its argument, which is that the point of the rule was to prevent and/or punish anyone who made it impossible for a man to support his family.  That includes corporations not paying an appropriate wage.

I mean to say, wot?

Anyway, my main point is this: just how often did this happen that there had to be a rule for it?  It’s like the warning labels that infest our lives: Don’t use this hair dryer in the shower. This chef’s knife is not meant to be used as a screwdriver. That kind of thing. It’s a given Stand-Up Comic’s Take that these warnings exist because SOME IDIOT DID THE THING, KENNETH, so what was the deal in ancient Israel?  First of all, were the men always wrestling, and if so, why were their testicles even in evidence?[2]

And had it become a problem that wives would throw themselves into the arena to give their husbands an assist?  What was this, the Judean Federation of Wrestling?[3]  I mean to say…

This realization puts the prohibitions of Deuteronomy and Leviticus in a whole new light.  They’re just warning labels.  For stupid people.

You’re welcome.

—————

[1] That’s just context.  The entire mindset is stupid.

[2] …nudity also being a huge shanda for the Chosen People.

[3] Not to be confused with the Judean Wrestling Federation[4]

[4] You’re welcome.

Gin, Part II

You will recall that on Monday I began making gin.

Yesterday I finished making gin.  This is a true thing.

On Monday, I put some juniper berries in some vodka to soak for 24 hours.  On Tuesday, I added what we in the gin industry refer to as “botanicals”:

There’s angelica root, gentian root, star anise, lemongrass, lemon peel, black pepper, and lovage (which had survived in the garden enough to give me what I needed).  Based on cursory reading on the intertubes, I measured out two grams of everything and dumped it all in.  It steeped overnight.

Yesterday I began taste-testing it, and by lunchtime it was clear that the botanicals—the lovage in particular—were threatening to overwhelm the gin qua gin.  I strained everything out, doubled the amount of vodka to dilute it, put more juniper in, added some coriander, and let it ride until cocktail hour.  Then I strained it all out, bottled it, and began testing it.

Okay, so… it’s not a sippable gin.  This will never compete with Ayrer’s Single Malt Gin from Nuremberg, for example.  More work is required before I get to that point.

However:

Gin & tonic: quite delectable.

Negroni on the left; Bijou on the right.  Both were good; although I was apparently not in the mood for a Negroni, I finished the Bijou with relish.

And then…

The Smoky Topaz. Oh my.  My recipe calls for barrel-aged gin, but this gin added several other dimensions to this most fabulous of cocktails.  That which is a too-strong presence of lovage when you sip the gin straight becomes a fantastic lingering undertone in the Smoky Topaz.

And so…

The trick will be seeing if I can repeat it.

New friends

I went out to see if there any lovage in the herb garden and found that I had acquired some new friends:

Aren’t they beautiful?  They arrive every year to feast on the dill, which I do not begrudge them in the least.  There’s plenty to go around, after all.

We will not dwell on the fact that I never see any cocoons, which means that either they go somewhere else to do that or most of them are eaten by friendly birds.

Gin.

Oh, just making gin, as one does.

That’s the concoction on the right.  The stuff on the left is just your average lemongrass-infused vodka for a new cocktail I’ll work on for the beach this weekend.

The gin is in its first stage: juniper berries soaking in vodka.  What, you thought gin was something other than vodka with plants in it?  Pfft.

Of course there’s no one recipe for gin.  You can find tons on the intertubes—everyone has a different combination of botanicals they like to use—but they all start with soaking the juniper berries for 24 hours, then adding your other stuff for 36 hours.  That’s right, boys and girls, you can craft your own gin in two and a half days.  What’s not to like?

My original plan was to use lovage from the garden, but the lovage has been stupidly whiny this summer.  Maybe there’s enough to use anyway.  I’ll keep you posted.

Otherwise, here are the most likely additions:

Mine’s going to be more spicy/peppery than citrus.

I wonder if it’s going to be drinkable?

New mystery plant

I have not blogged regularly, mainly because the situation in our country is so grotesque that I can’t keep up and I don’t want to spend all my time with my readers picking at the scab that is our Current Embarrassment.

So here’s a post about out of control plants.

You may recall the Dill Plant That Ate Newnan and/or the Cardoon that Couldn’t Be Stopped.  Both are now gone, because I ripped them out of the ground and ruthlessly discarded them.

But oh so quietly last year, a delicate little vine sprang up in the side patch where the cardoon was.  I gave it a little frame to grow onto (to keep it from latching onto the shrubbery).

This year, of course, it has come back more determined, and so I’ve built it a large frame just to see how far it’s willing to go:

It has responded with enthusiasm:

…although it still seems to be looking for ways to devour the shrubbery.

Why am I allowing an obviously invasive plant to thrive in my garden?

It has these beautiful little flowers.  I want to see if I can create a tower of the feathery leaves and brilliant red blooms.

Stay tuned.

What am I not getting?

This is a serious question: what is the Current Embarrassment trying to pull?

I know, we could spend the rest of the night giving examples of his unprecedented lying, but let’s do just one: at last night’s rally in Phoenix, he enthused (via Twitter, of course) about a “beautiful turnout of 15,000 people” at his re-election rally.[1]  The fire marshal tells us that the venue’s limit is <5,000 people.

He lied.  Everyone who is paying attention can see for themselves that he lied.  He told the crowd that CNN was not covering his shockingly honest statements—which the rest of us watched on CNN. He told the crowd (of less than 5,000 people) that there were no protesters outside, which every major network was able to show immediately was not true.

Sure, he’s playing to his rapidly dwindling base of dyed-in-the-wool ragebunny amygdalas, but the rest of the nation—the rest of the world, KENNETH—can see that he’s lying.  We all know it. He’s lying.

So, again, my serious question: what is he trying to pull?

—————

[1] His re. election. rally.  He’s been in office seven months, and he’s running for re-election.[2]

[2] On the other hand, he could be attempting to govern.

The Fault, dear Brutus, lies not in our stars

Last Friday I had occasion to visit Peachtree Publishers in Atlanta and meet their president Margaret Quinlin.  She gave me a copy of their newest big publication, Fault Lines in the Constitution: the framers, their fights, and the flaws that affect us today, by Cynthia Levinson and Sanford Levinson.  It is a triumph and this is a rave review.

The book is aimed at the middle reader, but as far as I’m concerned every sentient being in this country[1] should read it and discuss it everywhere.  The authors are thorough, honest, and more than a little skeptical about the solidity of our governing document.  They have reason to be.

A little background: back in 1987, at the bicentennial of the Constitutional Convention, the Newnan-Coweta Historical Society asked the Newnan Community Theatre Company to come up with some kind of presentation/performance for them that addressed this epochal moment in our history.  It fell to me as artistic director at the time to devise the entertainment.

That summer, at GHP, I read the complete The Records of the Federal Convention of 1787, compiled and edited by Max Farrand.  Even though the delegates worked in absolute secrecy and the recording secretary burned all deliberations, James Madison kept copious notes (which he edited selectively later in life).  To this document, Farrand added all other diaries/letters/correspondence that he could find, and the result is a fascinating read.  Those men argued over everything: every word, every comma, every idea.

The point is that the Constitution we ended up with was by no means foreordained.  In fact, the eventual performance piece NCTC came up with asked the audience members (seated in groups relative to the size of the thirteen colonies) to decide the nature of the Executive, and both nights they dumped our current arrangement in favor of a single executive elected for a single term of six years.  Expecting a worshipful experience of a perfect document, they were surprised and delighted to be shown there was more to it.

Fault Lines covers this concept of argument and compromise brilliantly.  Each chapter follows the same outline:

  1. Introductory story of some recent foofaraw which illustrates a problem springing from the Constitution as written
  2. “Meanwhile, back in 1787…”, in which the debate over the problem is discussed and the reasons given for the final decision
  3. “So what’s the big problem?”, which details why the compromise has unraveled or caused problems, often because of vagueness in wording or the founders’ astonishing lack of prescience for 200 years in the future
  4. “There are other ways”, outlining how the states and other countries deal with the issue (spoiler alert: there are other ways)
  5. “The story continues” with the authors looping back around to the introductory story and giving us the upshot

The final section is the most agitating, in every sense of the word.  The authors grade the Constitution and how well it has delivered on the promises in the Preamble.  (It gets an overall C+.)  Then the authors, responding to James Madison’s comment that “it is incumbent on their successors to improve and perpetuate it,” list some very uncomfortable ways we might go about doing that:

  1. Change Senate rules (i.e., get rid of the filibuster)
  2. Pass new laws (mostly about the structure of representation)
  3. Develop work-arounds to the Electoral College
  4. Amend the Constitution, with a long laundry list of items derived from the discussions in the rest of the book

Finally, the authors have a one-on-one debate as to the wisdom of going full Leeroy Jenkins with a Constitutional Convention to upset the entire apple cart.  It’s enough to keep you up at night, which at this point in our history is saying something.  (I should say that the book is very current, referencing the current administration and some of its actions.  The section on the 25th Amendment is particularly pointed and reflects some of my own writing, here and here.)

So, teachers, want a resource to celebrate our annual MANDATED CONSTITUTION DAY LESSONS COMRADE[2] on Sep 17?  Requisition a classroom set of this bombshell and watch the children’s minds crack open.  And probably their parents’ heads explode.

—————

[1] I am aware this does not include everyone in this country.

[2] I’m actually in favor of requiring the study of the Constitution, just probably not in the way that the über-patriots who have mandated it intended.

Witless

Here’s an article from the New Yorker, “Why is Donald Trump Still So Horribly Witless About the World?”  Go read it.

As hard as it is for me to believe, there’s still that 27% hardcore lump of citizens who think the Current Embarrassment is actually being successful at his job.  To them, it’s a good thing that he’s like a coked-up bull in the china shop of the world stage.  “Heck yeah,” they shout, “USA! USA! Kick butt!”  Or words to that effect.

It does not seem important to them to take into account All The Things that make up international relations, not history, not protocol, not expertise.  They live in an imaginary world where the Middle East is all terrorists (except for Israel); China is a backwards Maoist dunghill; and the U.S. acts unilaterally no matter what the circumstances might be.  USA! USA!

They never see that, like their leader, their ignorance and bluster will not produce the results they were hoping for.  They’re just glad they finally have someone who will disregard all those effete intellectuals and Make America Great Again.

So let me present an analogy that I imagine many of them will find relatable.  Feel free to share it with your witless uncle.

You’re at work.  You like your job.  You like your company.  You’ve worked there for a long time, and you’ve gotten to know the ins and outs of the command chain, the production process, the purchasing process, the company’s competitors.  You know who to go to in order to get things done: Marcia for requisitions, Bill for project management, Laketha for personnel.  You know Rachel can’t be trusted to keep a secret and Austin’s a backstabber.

Then they hire a new boss. Let’s call him Ronald.  Ron.

Ron is pig-ignorant.  He’s never even been in the industry before, and it doesn’t look like he wants to learn about it.  He got hired because he can “shake things up.”  You know the type.

So Ron issues memos that don’t make sense and often conflict with company policy.  He makes everything personal.  He fires Marcia.  Bill quits.  He reorganizes your department in ways that are confounding.   He promotes Austin because Austin sucks up to him.  He does not ask for input, nor will he listen to anyone who offers it.  He’s degrading and abusive in meetings; Laketha has left in tears more than once.  He will not sign off on your vacation time.

Ron insults your partners and sets up meetings with your competitors.  He cancels longstanding contracts with suppliers.  He announces changes to the product line that have not been tested or approved, and if implemented will destroy the company’s bottom line.  He’s the epitome of both Dilbert‘s Pointy-Haired Boss and The Office‘s Michael Scott.

In other words, Ron walks into the job and ignores everything that’s important about the job and the company.  He dismisses it.  He shakes things up.

The Current Embarrassment is that guy.  He’s your nightmare boss Ron, only with nuclear codes and China and the U.S. economy at stake.

And that is why expert after expert has abandoned longstanding tradition and uses words like “witless, clueless, appalling ignorance, studious rejection of in-depth knowledge, unteachable, completely irredeemable” to describe him.  This is not some liberal plot to discredit the man. This is Marcia and Bill and Laketha (and you) trying to get the shareholders and the board to understand why the man has got to go.