Tag Archives: Ask Brian Anything

Brian answers: Poltroons, pantaloons, and poetry

My friend Brianna writes:

In the ‘etymology’ category: what are your top 5 (or some generic enumerated list of your defined length) favorite words & why? There’s some cool etymology out there, and after taking Latin I realized why some weird words exist in English.

Also, what’s something that you enjoy talking about that people don’t ask you about enough? (Or, worded differently: a topic for which it’s hard to find a conversation partner?)

What do I think about this question?

Y’know — in a good way.

An etymology, for those who don’t know, is the origin of a word. For instance, coffee is from Italian caffe, from Turkish kahveh, from Arabic qahwah, according to the fabulous and endlessly fascinating Etymonline.com (which I used as a resource for much of this post). Most etymologies are like that — a gradual evolution from one language to the next, culminating in the English word we know today.

But some etymologies are different. For instance, the etymology for chortle is Lewis Carroll made it up in 1872 so now it’s a word, b****es. (I’m paraphrasing slightly.) But yeah, in Carroll’s novel Through the Looking-glass, the sequel to Alice’s Adventures in Wonderland, there’s a poem called Jabberwocky. It’s full of nonsense words like chortled, cleverly crafted so they sound like they mean something, but it’s hard to say exactly what. Most likely, chortle was formed by chuckle + snort.

By the way, if you’ve ever heard about someone galumphing along, that’s also from “Jabberwocky,” evidently gallop + triumph.

Think about that for a minute. One poem, 24 lines, at least two new words added to the dictionary. That’s an average of one new word every 12 lines. I mean, c’mon.

Okay. Enough about Carroll.

Another of my favorites is atonement. I read somewhere that it was formed by at + one + ment, as in, becoming at one with something or someone. I’m suspicious of such neat and convenient origins — false etymologies are a dime a baker’s dozen — but that one turns out to be true. Which is pretty cool, I say.

Some etymologies are fun just for the winding route they take. For instance, panties is a derivative of pants, which is a shortening of pantaloons, which comes from — and this is where it gets cool — Pantaloun, a silly old man character in 16th-century Italian comedy who wore tight trousers. He, in turn, derives ultimately from a person who may have actually existed, one Saint Pantaleon, whose name means all-compassionate.

That pan prefix, meaning all, pops up in lots of places. For example: Pangaea, a prehistoric supercontinent that combined all landmasses into one — hence pan (all) + gaia (earth). So Pangaea and panties use the same pan, albeit by an awfully circuitious route.

On a more serious note — one etymology I’ve never been able to get out of my head is the origin of excruciating. It has the same root as crucify — the Latin crux — and it suggests the pain of dying on a cross. Knowing that, I tend to use the word sparingly, as few pains are really awful enough to warrant that description.

What else? Well, al is Arabic for the, so a number of English words starting in al are ultimately from Arabic: algebra, algorithm, alchemy, alfalfa. If you’ve got one of those uncles (and everyone does) who don’t trust furrign-soundin’ names like Al Jazeera, remind him not to have any alcohol either. (You, on the other hand, should feel free to imbibe.)

Speaking of Arabic — it’s remarkable that so many Americans see Allah as a name completely different than God. Like, if you asked someone the name of the Jewish, Christian, and Islamic God respectively, the answers would be: God, God, Allah. Same, same, different. Right?

Well, it’s not wrong, but it’s awfully misleading. God in the Old Testament is (usually) a simple translation of the Hebrew Elohim. So a fair comparison between Judaism and Islam would be Elohim and Allah, or else God and God. And if you’re thinking that Elohim and Allah sound kinda similar, congrats — sure enough, the Arabic derives directly from the Hebrew. It’s the very same word.

(Brianna — if you have any cool etymologies to share, Latin or otherwise, feel free to leave ’em in the comments!)

Completely apart from etymology, there are some other words I enjoy just because:

  • sockdolager — a decisive, knockout blow
  • poltroon — a coward
  • defenestrate — to throw (something or someone) out a window
  • mumpsimus — someone who insists on “correcting” others into an error (e.g., when you say “He went with Tara and me” and they insist it should be “He went with Tara and I”)
  • apotheosis — the process of becoming a god
  • dithyrambic — in the manner of a wild, ecstatic song
  • balderdash — nonsense
  • codswallop — nonsense (British)
  • Brobdingnagian — huge
  • paean — a song of praise
  • sesquipedalian — an adjective describing very long words
  • antediluvian — before the Flood
  • skiey — related to the sky (yes, really)
  • ruth — what you lack if you’re ruthless (yes, really)

The words listed above are odd or obscure. But I also like a lot of words that are reasonably common, because they’re strong, evocative, or beautiful. Words like:

  • brandish
  • livid
  • murmur
  • sanctum
  • hallowed
  • immaculate
  • sovereign
  • sordid
  • somber (I guess I like so- words?)
  • lull

As for your second question — What’s something that you enjoy talking about that people don’t ask you about enough? Man, that could be a whole blog post in itself. In no particular order:

  • Etymology
  • The Byzantine Empire
  • Alchemy
  • Palindromes, anagrams, and other word games
  • The poetry of W. B. Yeats
  • Whatever Elon Musk happens to be doing right now
  • Buffy the Vampire Slayer
  • Avatar: The Last Airbender
  • … and about a hundred other shows, books, movies, etc.
  • Cognitive biases and logical fallacies
  • Comparative mythology
  • Copyediting
  • The Zelda games Ocarina of Time, Majora’s Mask, and Link’s Awakening
  • The Bible
  • Crazy math stuff like Graham’s number
  • Batman
  • Cosmology (the large-scale structure of the universe) — stuff like galactic filaments
  • The legends of King Arthur
  • Artificial intelligence
  • Cool geography, like Lake Baikal and the Eye of Quebec
  • … and, of course, Crane Girl 🙂

As you’ve possibly guessed by now, I could keep on going till my keyboard breaks from attrition. I’ll stop there. But thanks for giving me the chance to ramble.

What about you, hypothetical reader? What’s something that you enjoy talking about that people don’t ask you about enough? Seems like a great question to open up the hidden corners of someone’s brain.

Anyway, that’s the end of the questions. Thanks, everyone, for another successful round of Ask Brian Anything. Have a weekend of Brobdingnagian proportions!

Brian answers: Prose and programs

My friend Josh writes:

Could you compare and contrast your experience with writing code and writing literature? Personally, I think they share many things in common, such as rhythm and flow, common structures/patterns, and opinionated naming/spacing/etc. You did a blog a while back about simplifying language in sentences and that also reminded me a BUNCH of simplifying code.

This is an excellent question. Someone could write a whole book on this topic, and maybe someone already has. I’ll try to restrain myself.

As you mentioned, lots of parallels jump out immediately:

  • There’s a first draft, editing/revision, and a polished “final” version that often still changes.
  • Quality improves when you get someone else to help with revision.
  • You want to be clear and concise — all else being equal, shorter is generally better.
  • You need to be skilled at a low level (syntax/grammar), at a mid level (functionality/meaning), and at a high level (structure).
  • Literature even has something akin to “debugging,” i.e., Why doesn’t this scene work the way I want?

But there are huge differences too.

For instance:

It’s a lot harder to be a mediocre programmer than a mediocre writer.

And a lot more impressive, too.

Why? Because almost everyone can write English to some degree, so becoming a “writer” just means honing those commonplace skills by some ill-defined amount.

Programming, by contrast, requires a completely different kind of thinking — it’s a specialized skill that most people simply have never learned. (It’s getting more common, sure, but it’s still relatively unusual.) Programming means thinking logically and mathematically. If you can program reasonably well, that’s pretty cool, IMO. If you can write reasonably well, that’s nice too, but, y’know, get in line.

Also, programming has a higher bar to entry. Anyone with a pen and paper, or a text editor, can write a story. But to program, you first have to:

  • Figure out what programming is and how it works
  • Pick a language
  • Write a program
  • Figure out how to execute your code (which may require getting a compiler)
  • Fix your syntax errors
  • Debug your runtime errors

You can have syntax errors in English, too, and mediocre writers usually do. But nothing pops up and forces you to fix them.

On the other hand, becoming a master writer and becoming a master programmer are about equally difficult, I think. In either case, you’ve moved beyond just the basics of syntax, grammar, spelling, etc. You’re looking for clarity, purpose, elegance, and beauty, and I think that’s equally demanding in either medium.

A writer has one audience, but a programmer has three.

A writer writes, a reader reads. Fairly straightforward.

A programmer, though, has to keep three audiences in mind all the time:

  • The computer
  • The end user
  • Other programmers

The computer is the most immediate audience. The code has to run properly there, or the whole thing falls apart.

The next audience is the end user. Even if everything runs okay at a technical level, the program still has to work like the user wants.

Finally, the code itself has to be written in a way that’s clear and easy to follow so that other programmers can maintain it.

For writers of literature, the reader fills all three roles. The reader is the end user; the reader “executes the code” in their own brain; and the reader sees the source code. In my opinion, this makes things quite a bit simpler for English writers.

The world of programming changes very quickly.

In IT, new languages pop up constantly. New libraries pop up even faster. New standards, new design patterns, new IDEs, new hardware, you name it. Keeping up with the changes is a full-time job.

Yes, a lot of the fundamentals of programming apply just as much today as they did thirty years ago. But you still have to keep up. As the Red Queen says: “Here, you see, it takes all the running you can do, to keep in the same place.”

English changes too, but compared to programming, the pace is positively glacial. Pick up a 100-year-old novel and the style will only seem slightly antiquated. Pick up a 10-year-old program and the first thought will be, “How can we get this up-to-date?”

Standards for programming are far more rigorous and precise.

Almost anything you do as a programmer is governed by a standard. Python syntax is extremely well defined, and it is defined by a single specification. User interface design? There are standards for that. Software structure? Standards for that too. Not all of it is perfectly defined, to be sure, but there’s a remarkable degree of clarity about what you’re “supposed” to do.

English has standards as well, but they’re a lot fuzzier.

Even at the most basic level — spelling, grammar, punctuation — there is no single, precise standard. Dictionaries differ, and none is universally accepted as “the” dictionary. The same goes for style guides. And even if there were a gold standard, there would always be exceptions, because language is fluid and slips out of any mold.

At the higher levels — plot, character development, style — things get even fuzzier. Sure, there are recommendations and guidelines, but they’re often contradictory, and many of the best stories throw them out the window. The only real advice is “Figure out what works, and do that.”

This makes life harder for programmers — but easier too.

Harder, because there are a lot more hoops to jump through to get it right. But easier, because someone actually tells you what to do. I don’t want to minimize the independence and creativity that programming requires, of course. But as a writer, I can’t even imagine a document, or set of documents, that could outline English with anywhere near the precision of a programming language.

As I said, I could probably ramble on for years hours, but I’ll stop there.

Anyone who hasn’t asked a question yet, feel free!

Brian answers: Young and old

The next two questions come from Dave, who is my dad, and thus part of the reason I’m so freakishly tall and bad at singing.

You being a writer and editor, and now a father, have you given any thought about writing a children’s book?

I haven’t, which is strange in retrospect, because it does seem like a good fit. I’m not great at drawing, but I bet I could whip up some cool illustrations in Paint.NET.

The ideas are coming to me already:

  • Kosh’s ABCs (spoiler: V is for Vorlon)
  • Why You’re So Small and Bad at Things
  • Let’s Count to a Googolplex

Seriously though, a kids’ book would be an intriguing challenge.

The hard part would be getting it published. From what I hear, the market for children’s books at the national level is extremely competitive. And that’s compared to the market for novels, which is already very difficult to break into. Most likely I’d have to find a small press, or self-publish, or make something just for Evan. And that’d be fun, too.

Second question:

Have there been occasions that have caused you to feel old yet?

Betsy and I often joke that we were born old, and we’re only half joking. We tend to stay home on weekends. We don’t like loud music. We don’t care about sports, or concerts, and we try to avoid parties. I only got a smartphone for the first time this month. I make noises when I sit down or stand up. I’ve always been forgetful about day-to-day stuff.

So at one level, I don’t feel too old, because I never did a lot of the things people associate with youth. (Wow, that came out more depressing than I intended.)

I guess it hits me most when I find out that stuff from my childhood happened a long time ago. Like — Star Trek: First Contact came out twenty years ago. How is that possible? It came out in the 90s! Yeah, it turns out the 90s were twenty years ago.

The actor currently playing Spider-Man was five years old when the first Spider-Man came out.

There are adults who aren’t old enough to remember 9/11.

Yeah. So, I try not to think too hard about stuff like that. 🙂 Everything changes.

Anyone who hasn’t asked a question yet, fire away!

Brian answers: Advice to an editor

The first question comes from blog reader backstorycat, who writes:

Hey Brian!
I’m a new editor trying to break into the publishing business. I’ve been freelancing pro gratis for several years now, and am currently applying to a few publishing houses. I’ve already taken a few post-graduate classes in editing and completed an internship. Unfortunately it’s a tough job market, and I’m beginning to lose heart. Any advice?

Hi! Thanks for the question.

First, I should mention that I’ve only been editing professionally for about two years myself. The very beginning of my editing journey was in February 2015, when I signed up for a subscription to the Chicago Manual of Style. It wasn’t until June 2015 that I landed my first paying job, and even that offered a very modest salary.

So this may be the blind leading the blind, to some extent. And probably some of my advice is stuff you’re already doing. But here we go.

First, you said you’ve been freelancing pro gratis, for free. Have you tried freelancing pro [I don’t know Latin] money? That might be a good intermediate step, a way to build a solid professional resume that can help you land a bigger job. Or you might find that you like freelancing and want to keep doing that full-time. Many people do.

There are a lot of ways to ramp up your freelancing. Talk to your past clients, and see if they have any paying projects, or know anyone who does. Do some searching and find indie authors, and cold-email them to offer your services. As for publishers, you might want to start small — there’s an enormous searchable database of small presses, and again, don’t be afraid to send out emails offering to edit for them. I’m not saying you should spam, of course. Do your research, choose your targets, tailor each email to its audience. But cast a wide net.

You say you’ve taken classes and done an internship, which is great. You might consider joining the Editorial Freelancers Association (EFA). Membership is a bit steep, but I’ve found it very useful, and it looks good on a resume. If you’re a copyeditor, consider joining ACES. I belong to both, and I’ve found the EFA to be the more useful of the two, but ACES is cheaper and also looks good on a resume. Both offer a variety of networking and job-hunting opportunities, among other things.

Since you’re relatively new and relatively inexperienced, consider doing free sample edits. Many editors scorn this practice, saying that their time is valuable and they should always get paid, whether it’s for sample edits or taking editing tests or anything else. Well, my time is valuable too, and I’ve gotten a number of paying jobs that way, so in my opinion, it’s worth it for less-experienced editors. Or, from the client’s point of view — why should they take a chance on an unknown editor of uncertain ability, without some proof of their skills?

I’d also suggest becoming a jack-of-all-trades. The more skills you have, the more job opportunities there are. If a client wants me to do something that I’m not currently qualified to do, my standard response is, “I haven’t done that before, but I’d love to learn.” If you specialize in Chicago style, try picking up AP or APA. Never fact-checked before? Give it a shot. Not sure how to edit Australian English? No time like the present. As long as you’re (1) open and honest about your lack of experience, and (2) willing to spend the time on research and do the best job you possibly can, it’s a win-win.

Of course, you also want to be sure that your core editing skills are very, very strong. If you’re a copyeditor: Read your preferred style guide cover to cover and take notes, if you haven’t already. You should have an opinion about when to use “judgment” vs. “judgement,” and “toward” vs. “towards,” and “gray” vs. “grey,” and “blond” vs. “blonde,” to name only a few. You should have a strong opinion about whether it’s okay to end sentences with prepositions, and whether the singular “they” is acceptable, and whether it’s all right to use “literally” as an intensifier. In other words, when you take an editing test, you want to be confident that you can not only pass, but impress.

If you’re an American editor — and maybe even if you’re a non-American editor — you really should have a copy of Garner’s Modern English Usage. If you have a dictionary, but you don’t have Garner’s, you’re flying blind. That’s how important it is.

I’d also recommend a paid subscription to the Unabridged Merriam-Webster Dictionary. It might seem strange to pay for this when the regular Merriam-Webster is free, but you get two major benefits. First, as implied by “Unabridged,” you get more words — a lot of relatively obscure (but potentially important) stuff that the regular dictionary just doesn’t have. And second, the paid version has no ads, which means the pages load faster, which is really nice when you’re looking up a bajillion words. The subscription is only $30/year, which isn’t bad, IMO.

If you use Windows and MS Word, and especially if you’re a copyeditor, consider getting PerfectIt. It’s basically spellcheck on steroids, and it’s caught countless little mistakes and inconsistencies that I wouldn’t have noticed otherwise.

Oh, and if you don’t have a professional website, I’d strongly suggest making one. Not only does it make you seem more professional yourself, it also gives potential clients a sense of what you’re all about. In fact, I met my most recent client when they emailed me and said they wanted me and no one else, because they could tell from my website that we’d be compatible. It really does make a difference, IMO.

As for social media … I think you could go either way. Being active on Twitter or Facebook can certainly be helpful, but it’s mostly helpful if you’re already interested in, or even excited about, communicating that way. If social media sounds awful and you create an account just for the sake of self-promotion, your lack of enthusiasm will probably come through in your tweets/posts, and you may be better off focusing your energy elsewhere.

Whew! That’s a lot of info I just dumped out there, and I could probably ramble on for another hour. Did I answer your question? If you have any thoughts or follow-up questions, by all means, leave a comment.

I’ve got four more questions in the queue already, and I’ll get to those soon. But if you haven’t asked a question yet, you’re still welcome to do so. Keep ’em coming!

Ask Brian anything!

It’s time once again for … ASK BRIAN ANYTHING.

What do you want to know? I’ll answer any question, even personal stuff. (The answer might be “I’m not going to tell you,” but hey.) Possible topics include:

  • Writing, editing, books, ampersands & pilcrows
  • Fatherhood
  • Software development (I’m no longer in IT, but I still write literally dozens of lines of code per year)
  • Depression
  • President Trump’s ongoing quest to make history remember Joseph McCarthy fondly by comparison
  • Religion(s)
  • Buffy the Vampire Slayer
  • Etymology
  • Anything whatsoever
  • Wait, not THAT! … oh, okay, even that

And … go!

Brian Answers: 30-Second Demosthenes

Fatal PC problems and super-duper tiredness have conspired to keep me away from the blog, but no more! Today I return (hopefully for good) to the final day of Ask Brian Anything.

Shaila Mudambi asks:

If you could make a 30 second speech to the whole world (everyone actually listening) what would you say?

I thought about this question for a long time Sunday, as I was mowing the back yard. What would I say?

Since I’m a hopeless romantic, I’m tempted to make some grand unifying gesture, calling for peace or understanding or goodwill, something like that. Or perhaps read a poem – Kipling’s “If” comes to mind, though it’s too long.

Except, the world is full of such gestures, and I doubt it would faze most people. If I want to make a difference, I decided I should try something more concrete.

I think I would find out the name of somebody in need, in a country plagued by war or disease. I would tell their name, who they are, and what challenges they face. Then I would ask for people to donate what they can to Doctors Without Borders to help that person.

It’s actually not about that particular person, whoever they are. I just want people to give. But countless experiments have shown that people are more likely to give if they have a specific person in mind. Paradoxical though it may be, we’re hard-wired to care more about one person’s suffering than a million’s. So I am being a little manipulative here, but I can’t say I feel too bad about it.

Thanks for an excellent question, Shaila!

Finally, “no1isordinary” asks:

Through what lens do you craft your answers?

To be honest, I don’t entirely understand this question. But I suppose the answer is something like “my mind” or “my life experience.” And since this blog is a reflection of my mind, you could say that the place I write my answers is the lens. DEEP! 😀

Well, that’s it for Ask Brian Anything. Thanks for playing along! It’s been fun. Regular posts resume tomorrow.

Brian Answers: The Deadly Truth

On today’s edition of Ask Brian Anything, blog reader LS asks:

Is 2+2=4 a truth you are willing to die for?

In yesterday’s post, I claimed the truth is beautiful and important. Today I have to answer: how important?

First, let’s distinguish between knowing the truth and telling the truth.

Knowing the truth is crucial as a foundation for your own thought and action. What you know stands among the pillars of who you are. But knowing the truth isn’t just about memorizing facts. It’s about curiosity, a passion to acquire new knowledge. It’s about weeding out lies and false beliefs. It’s about using the same carefully structured doubt that lies at the heart of the scientific method. Knowing the truth is a way of life.

Telling the truth is more complicated. Passing the truth on to others is important for its own sake, but it also establishes trust, the foundation of a healthy relationship – and a healthy society. Lying erodes trust, and that’s dangerous.

Knowing and telling the truth are both virtues, but neither is the highest virtue. It’s easy to imagine scenarios where you should lie to protect someone’s life, and with a little more imagination, we can even think of times when it’s nobler to delude oneself than to face the truth.

So, with all that in mind: is 2+2=4 a truth I am willing to die for?

It depends.

The question conjures up visions of a Winston or a Picard in some Orwellian chamber, with a brutal interrogator bent on shattering his basic understanding of reality. It suggests, more than just an equation, a titanic struggle between individual good and bureaucratic evil.

And so I say again: it depends. It depends what the stakes are.

If it’s just about me, my own understanding of reality, I don’t think I’d be willing to die for that. But if somehow my struggle determined the fate of something larger – if I could save the lives of others, or steer the course of a society – then yes, I’d probably be willing to die for that.

In other words, I wouldn’t die for the truth itself, but I might die for the implications of the truth.

Ideally, however, nobody dies! Ideally, we would eat cake and talk about Star Trek. You know, just sayin’.