I dream of chyron

My dad was telling me recently that he had a dream about a strange word. (He knows his audience.) In the dream, the word seemed perfectly normal, but when he woke up, he realized it was unfamiliar, and wondered if his subconscious had invented it.

The word was chyron.

I was excited, because I actually knew that one! I said it was a real word, and it means the headline banner they show at the bottom of news shows:

Afterward I looked it up to confirm, and my memory was correct. I also learned how to say it: KYE-RON (it rhymes roughly with pylon).

This word was in the news (ha!) a year or two ago, part of the swirling clusterfudge that was the 2016 election. So maybe that’s where my dad’s subconscious picked it up.

What’s especially cool, though, is that in his dream, chyron had an entirely different definition: it was a feature on the surface of a cloud. I think that’s a much better meaning, and somehow appropriate to the aesthetic of the word.

So now I’m wondering — is there a word for the surface features of clouds? And if not, what would you call them, since chyron is already taken?

Personally, I’m thinking pufftures. But I could be swayed.

Advertisements

Why you need a copy editor

this

Image

So it’s gonna be that kind of week

Haiku of Summer, month 3

I was planning to do a haiku per day for the whole summer. And I made pretty good progress: see month 1 and month 2. But in the third month … well, to paraphrase Alan Jackson, who was paraphrasing Eddie Cochran:

Sometimes I wonder
what I’m gonna do
’cause there ain’t no cure
for the summer haiku.

Life gets busy, time gets short, the poetry backlog gets long, and eventually you just gotta cut your losses.

Still, I completed 74 of a planned 94, which is 74 more than zero. So without further rambling ado, here’s what I wrote in the third month of summer:

#63 — 8/27/18
Concrete is cracking,
inch by inch, year by slow year.
Nature is pushing.

#64 — 8/27/18
Luminous, gibbous
globe wider than Kazakhstan
hangs in the treetop.

#65 — 8/28/18
Dawn light drips over
brick-and-vinyl horizon
and evaporates.

#66 — 8/28/18
T-shirt to be washed
lies limp on cool bathroom floor
dreaming of sunshine.

#67 — 8/28/18
Razor scrapes my skin,
once more rebuking nature’s
tiny excesses.

#68 — 8/30/18
Headlights plow darkness
like snowplows clear away snow,
piling shadows deep.

#69 — 8/30/18
Warm dusting of rain
taps out softly on my skin
messages from clouds.

#70 — 8/30/18
Old routine, routine:
worn thin, rearranged, re-trod.
Trails change; same old dirt.

#71 — 8/30/18
Lightning like anger
flashes distantly, thunders,
and gives meager light.

#72 — 9/7/18
Tonight I can see
why this pitted white crescent
was called a goddess.

#73 — 9/7/18
Turn signal, little
heartbeat, reminds its master
that a path can change.

#74 — 9/7/18
A long, jagged rip
in the cloudfront exposes
imperial gray.

Image

HEY YOU GUYS

Postmortem: The First Congress

I had a long dry spell — over nine months — where I didn’t read a single book from start to finish. I was still reading, of course: I started some books without finishing them, I read a lot of stuff online, I read 27 volumes of manga (Claymore — pretty good), and I read some books of the Bible (which I don’t consider “books” in the normal sense). Still, I’m glad I finally broke that bookless streak.

The First Congress, by Fergus M. Bordewich, gives a great insight into how the U.S. government really formed. In school, you learn about the Declaration of Independence, the Revolution, the Constitution … and then early U.S. history, like the Louisiana Purchase, Lewis & Clark, and the War of 1812. That’s all fine, but it does skip a very important step, something I’d rarely thought about before: How did we get from a piece of paper (the Constitution) to an actual, functioning government?

Picture it: The year is 1789. The Constitution’s just been ratified, replacing the weak-sauce Articles of Confederation. The United States are finally united, at least in theory — all eleven of them (North Carolina and Rhode Island haven’t accepted the Constitution or statehood yet). The first president, the universally beloved George Washington, arrives in New York City (the nation’s temporary capital). Congress arrives too — the House of Representatives has 65 congressmen, and the Senate has 22 (although it takes a while for all of them to show up).

You’ve got a quorum, you’ve got public support and goodwill, you’ve got this fabulous piece of paper. What you don’t have is any federal government whatsoever, apart from yourselves. Your country is militarily weak, massively in debt, full of internal divisions, and not generally expected to survive. You have few resources, no federal laws, no precedents, and no judicial branch whatsoever at the federal level. You need to build an entire government from scratch, following a structure that’s never been tried before. And you need to do it right now.

And … go!

It’s crazy, isn’t it? But The First Congress takes you to the center of the craziness and makes you feel like you’re really there. The author gives lots of quotes from everyone involved, letting you hear what happened in their own words. He shows the issues from all sides. What’s more, he offers all sorts of details on how life was back then, from food to newspapers to public sanitation.

Major lessons from this book:

  • The first Congress and the current Congress have a lot in common. Partisan gridlock, pettiness, and scandal are nothing new. We worry about gerrymandering (and rightly so), but the first Congress included the original gerrymander-er, Elbridge Gerry himself. The bickering and infighting over where to place the nation’s permanent capital went on for a staggering length of time. For me, this insight inspires hope rather than cynicism, because it means we’ve conquered these obstacles before and we can do it again.
  • The Founding Fathers were just human beings. They were great humans who did great things, but they were all deeply flawed as well, in a variety of different ways. You often see some quote attributed to Jefferson or Madison, as if that alone makes it true — but Jefferson and Madison were both wrong (and naive) about all sorts of things.
  • Moreover, the Founders disagreed and argued constantly among themselves. That isn’t a criticism, just a reminder that the oft-cited “what the Founders intended” was often not any single thing. This whole states’-rights-versus-federal-power debate has raged from the very beginning. What does the Constitution really mean? Simply put, nobody knows, and nobody knew back then, either. (Of course, that’s not to say that all interpretations are equally valid.) In many ways, we actually have better insight into the Constitution today, because we have the benefit of learning from past mistakes.
  • Alexander Hamilton is severely underrated, the musical notwithstanding. As a kid, I wondered why he was on the $10 bill when he wasn’t even a president. It turns out that, in addition to living an utterly fascinating life, Hamilton was a crazy-smart economics geek at a time when “economics” was kind of a new thing. He built the U.S. financial system virtually from scratch, using debt in brilliant (and mostly ethical) ways to build up American credit at a time when a huge number of Americans regarded debt as inherently evil. And it worked.
  • John Adams, by contrast, comes across as rather overrated — at least in this author’s narrative. His fragile ego, frequent outbursts, opposition to free speech, admiration for glamorous foreign leaders, and general grandiosity, all remind me a little of a certain other U.S. president. (Relax — I said a little.)
  • Nothing is simple, especially in history. If someone tells you otherwise, tread carefully.

That’s all for today. Have an outstanding weekend!

Busy busy

Lots of stuff to talk about, but not much time for talking. My schedule next week should be a bit looser.

Hope life’s treating you well!