If
you thought the nature/nurture debate was settled, think again. Far from it,
even within the scientific community. Are genes the primary determiner of who
will get fat over time, is it the sum of their behaviors, or both?
An
article this week in Science News
reports on a study done by researchers at Massachusetts
General Hospital and the Broad
Institute (yes, really) in Boston. They looked at over 2 million genetic
variants from thousands of people and came up with a way to predict, they said,
a person’s likelihood of becoming “obese” (having a Body Mass Index of 30 to 39.9)
or “severely obese” (BMIs of 40 or higher). OK, that sounds useful.
OK, maybe you didn’t need to see this. Photo by Poznyakov via Dreamstime.com
But
hold on, other researchers said. Behavior can play a big role, too, maybe a
bigger one than a person’s genes. One suggested that if a person was told that
they were genetically destined for severe obesity, they might give up and not
take any preventive actions, like managing their diet.
Others
complained that the algorithm failed to identify a significant fraction of
those who actually did become severely obese, almost 75% of those in one part
of the study group. It even identified some people as having the lowest probability
of becoming severely obese, yet they did.
So
is this test really all that helpful? I’d have to say not in its current form.
I wonder how it would have flagged me. My BMI is a little above 25 and my
doctor keeps pushing me to lose a few more pounds. Easier said than done, as
you may know. I’ve change my diet and I’m exercising more. I’ve seen some fat
disappear but muscles bulk up, too, so I’ve lost fat but not necessarily
weight.
That
reminds me of something that happened a few years ago. The Air Force tried to
kick out an A-10 pilot they said was overweight. Turns out he was a weight
lifter and body builder. His body fat percentage was in the low single digits.
He was healthy but his BMI was way over the service’s limits. As I recall, the
Secretary of the Air Force had to finally weigh in and stop the pilot’s
ejection (both puns fully intended).
That
story illustrates the objections of some of those scientists. The pilot’s
behavior may have trumped whatever his genes tended him toward… or the two may
have worked together for his benefit.
So
was that study a bad one? No, it wasn’t. While the researchers may have made
claims for their algorithm that it couldn’t support, this is one step along a
journey. Better studies will look at more gene variants and will factor in
behavior too.
Does
“person A” come from a culture where people eat a lot of high-fat foods? Factor
that in. Does their family live that life, or have they switched to healthier
eating habits? Factor that in too. This could be a case where genes establish
tendencies but not destiny.
This
kind of work defines gaps in scientists’ knowledge that need to be filled in.
The study’s main benefit might actually be in having revealed those gaps.
I’m
ticked off this week. No getting around it; I am. But I’m also sad and
frustrated.
As
of April 11th, the Centers for Disease Control and Prevention reported that there
have been 555 confirmed cases of measles so far this year. That’s more than in
all of 2018 (372) and the highest number since 2014 (667). Measles was declared
“eliminated” in the U.S. in 2000, but that means the disease isn’t present all
the time (or “endemic”), not that it doesn’t exist at all.
Travelers
from countries where measles is still
endemic bring cases into the U.S. every year. Usually, there are enough people
who’ve been vaccinated around them that no one else catches the disease, or a
few do, and then no one else does. This is “herd immunity” at work.
But
there are states and municipalities around the country where people can claim
all sorts of reasons for not wanting to get vaccinated, or get their kids
vaccinated. As a result, not only are they now vulnerable to this disease—and a
lot of others—but so are the people around them.
Some
of these people cite religious beliefs. Some of them live in relatively small,
tightly knit communities like the Orthodox Jews in part of New York City.
Others are scattered throughout their cities like, say, Christian Scientists.
Or they live in isolated rural areas. I’m not happy about them for reasons I’ll
make clear later.
I’m
much more concerned about the ordinary but science-ignorant citizens who’ve
been suckered by the anti-vaccine movement into believing emotion-laden
allegations that vaccines cause all sorts of conditions, the most famous, or
infamous, being autism. Never mind that in the case of autism, the scientist
whose study started the whole thing retracted his research long ago, agreeing
with his critics that he’d made some pretty serious errors in his work and
conclusions.
But
the virus of fear has been released into the wild.
Medical
professionals and other scientists have tried to convince anti-vaxxers with
scientific data and statistical assurances. That’s worked about as well with
them as climate scientists arguing the facts with climate change deniers.
In
other words, it hasn’t. And it won’t.
Fear
is a powerful emotion, while facts have no emotional component. Fear will win
that fight every time.
Anti-vaxxers
have been making another argument, that it’s their “right” to decide whether to
have their kids vaccinated or not.
So
what about the right of other kids to be healthy and their parents free of the
fear that their kids will come down with some real and potentially terrible
disease? Apparently, that’s not important.
“I
care about my rights, but yours are irrelevant” is the attitude.
I
can think of a couple of other long-running arguments in our society that echo
the same themes. Bet you can too.
For
some time, conservative New York Times
columnist David Brooks has been advocating for a renewed sense of community in
America, here,
for example. His idea is that when people have compassion for others and are
interested in and concerned about their well-being, they bring their own selves
and their own rights into balance with those of other people. Those “others”
become real human beings again.
That,
it seems to me, is what is failing to happen here. The anti-vaxxers and the
others who refuse to get their kids vaccinated against preventable diseases
fail to care for the other children around their kids and about their health
and future. They don’t seem to recognize that there’s a connection between
their own children and those other kids, even when the children are all in the
same classroom or playground together. Their own kids—and their own decisions—exist
in a kind of bubble.
Except,
of course, that they don’t.
Sadly,
it’s natural in a situation like this, to respond to fear-driven emotion with
fear-driven emotion. But that’s only going to drive those fear-driven
anti-vaxxer parents deeper into their shells of denial. And then the problem
just gets worse.
Somehow,
a sense of community, of connectedness has to be snuck into these folks’
worlds. A community different than the anti-vax community they’re already in,
that us-against-the-world community. One that reconnects them to the wider
world, that leads them to accept that they have a moral responsibility not only
to themselves and their own families but to all of the people around them.
I’m
not sure where that change begins, or how, although I’m pretty sure it does not begin with a conversation about
vaccination. The first vaccination has to be against fear.
The
fundamental element of my Eternity Plague
series—The Eternity Plague (book 1), Chrysalis (book 2), and Wild Spread (book 3, currently in draft)—is
that five naturally-mutated viruses have infected all of humanity and are doing
all sorts of strange and not necessarily wonderful things to everyone. My
heroine, Dr. Janet Hogan, discovers the viruses and has to try to stop them
before they do too many awful things. Good luck with that: so far the viruses
are doing more things faster than Janet and her team can respond to them. How
will the series end? Sorry, no spoilers here.
But
because these books are science
fiction, I wanted to ground them in science, and good science at that. But having
the viruses cure and prevent all viral diseases and repair the genetic
mutations that cause others?
Uh,
yeah, that seems like a stretch. But that’s why I write “fiction beyond the
known,” right?
Now,
I’m not a geneticist like Janet is, nor do I play one on TV or in the movies,
so I needed to do a fair amount of research to be able to present things in a
credible but futuristic way, since the series is set in the mid- to late 2030s.
A ribosome
For
example, early in The Eternity Plague,
Janet and her team are deep inside a virtual reality simulation of a gene’s DNA
being run through a megamolecule called a ribosome, which “reads” the DNA and
creates a protein. I invoke other genetic machinery, including something called
messenger RNA to help make the protein, which it does in real life.
Later,
I involve “regulatory segments” of chromosomes, which are also real things. And
some of the plague viruses are powered by DNA, others by RNA, which is accurate,
too.
But
still: curing all sorts of disease? And then creating chrysalises around people
and transforming them? Really?
Well,
OK, maybe that’s still a stretch (let’s hope so, in the case of the
chrysalises, anyway!) but a
recent article in Science News magazine shows how scientists are
discovering the previously-unknown roles of various kinds of RNA molecules. Not
only are these roles new and unexpected, but the fact that there are so many
different kinds of RNA is a bit of a surprise too.
These
“non-coding” RNAs—RNAs that aren’t used to make proteins—do some significant
things:
Some of the 18,000 different kinds of “lncRNAs”
interfere with certain chemotherapy drugs;
Some “microRNAs” block other RNAs from being
read by ribosomes, which may push cells to become cancerous;
Left-over bits of the “transfer RNA” that normally
helps bring nucleic acids to ribosomes so they can build proteins, can also help
viruses reproduce inside cells.
In
each of these cases, and the others the article discusses, scientists are
working to understand how these RNAs do what they do so that they can find a
way to block the RNAs’ bad effects in the body. Which is what Janet and her
team are trying to do, just under a lot more time pressure and outside threats.
All
of which is a way of saying that maybe I wasn’t so far out there with what
these viruses and their DNAs or RNAs might be able to do in the human body. A
little bit of knowledge, a little bit (or a lot) of ignorance, and a dash of
imagination are all that’s needed to come up with a premise that might not be that crazy after all.
The
cliché “writing a book is like running a marathon” has, like all other clichés,
that kernel of truth that gets worn out from overuse. But the kernel remains
true.
Photo by Photostock, via FreeDigitalPhotos.net
I
got to thinking about this because, while I work on draft #4 of Wild Spread, I’m also getting ready for
my 19th consecutive year of volunteering with the Oklahoma City
Memorial Marathon. There are many parallels between writing the book and my
volunteer work—which I do to honor the memory of a friend who was killed in the
bombing of the Murrah Federal Building—the first being that they’re both important
to me. I’ve also completed one half-marathon and two books, so I can speak with
at least some knowledge of running
and writing.
The
other parallels between writing and marathoning include:
They require persistence. This is the obvious
one. Both require continuous, steady exertion and development in order to
complete the task. Runners and writers both build endurance and confidence over
time, and both must learn a lot along the way, about themselves and what it
takes to achieve their goal.
They take time. Writing a book—at least, writing
a good book—takes a year or more for many of us. Training to run a full
marathon, or even a half-marathon, can easily take as long. I trained for
several years before my half-marathon. My books invariably take years to
complete too.
Runners and writers start with the basics. Virtually
everyone who can walk knows how to run. Some, then, think they can run a
marathon. (Others think these people are mental. They may be right. See below.)
Virtually everyone who can spell (more or less) thinks they can write, and
therefore thinks they can write a book.
There’s SO much more than basics. Just because someone
knows how to run doesn’t mean they know how to run long distances, like 13.1 or
26.2 miles. Similarly, just because they can string a few sentences together
doesn’t mean they can come up with 15,000 to 20,000 sentences that work
together to make a coherent story.
“Ninety percent of baseball is half mental.” (Yogi
Berra)
Distance running and book writing are at least
as much mental challenges as they are physical. When you start running, the
idea of running five miles, much less more than 25, is intimidating. When you
start writing that first book, the idea of writing not just 10 pages, not just
100, but 300 or more is intimidating too.
Runners “hit the wall.” Writers hit writer’s
block. Both suck. And both have to be overcome somehow.
Going out for a training run on a cold, windy
day, or sitting down to write when you’d rather be doing just about anything
else also sucks. But the runner or writer have to do them, or something productive, anyway.
All
are conquered (or gotten around) mentally as much as physically.
Taking care of body and mind matters. Eating
right, staying hydrated, getting enough rest, and being smart about intake of alcohol
or other drugs, all help runners and writers get in top shape and stay there.
Some equipment required. But not much. Good
running shoes, proper clothing for different kinds of weather; that’s about all
a runner needs. A writer can make a lot of progress with a pen and a pad of
paper, although they’ll need a computer and printer eventually.
Support. Runners need sports bras or jock straps
(usually not both), good shoes, and maybe some other bands or braces, but what
they need most is other people to help and encourage them. Writers need that
emotional support too, whether it’s from family, friends, an agent, an editor, or
a quality writers’ group.
A place to work. Runners need a (safe) place to
run, writers need a place where they can focus on their work. Neither is likely
to be perfect; each just needs to be good enough.
A reward at the end. For a runner, feeling good
at the end of a training run is great, crossing the finish line on race day is
better, hitting a new personal best time better still. For a writer, holding
that proof copy in your hand for the first time, or receiving that contract or
first royalty payment makes all the time, struggle, and frustration worthwhile.
Getting
from the starting line/“in the beginning” to the finish line/“the end” takes
all of these and more. There are many would-be runners and writers who start
but never finish, whether that’s training or writing that first draft. Their dreams
die in the harsh, cold reality of just how hard each of these tasks is. But
some of these dreamers discover strengths and abilities they never knew they had,
and joys they never expected to experience. The only way each of us can find
out which will be our fate is to try.
This
is the last post in the series on characterization. Next time we’ll move on to
setting.
Photo by Jeroen van Oostrom, via FreeDigitalPhotos.net
If
you’ve traveled around the country, or watched TV or the movies, or done just
about anything other than live under a rock, you know that people speak
differently in different places. They have different accents, different slang
terms, and different styles of speaking. Compare the laconic Mainer or cowboy
to the fast-talking New Yorker. And that’s just in the United States!
Canadians, Britons, Scots, Irish, New Zealanders, Australians, and some Indians
and Kenyans (to name just a few) speak English, too.
And
they all do it differently.
England’s
WWII Prime Minister Sir Winston Churchill famously described America and
England as “two nations separated by a common tongue.” Love that line.
The
differences aren’t just geographic, either. There are differences between
racial and ethnic groups, economic classes, age groups, education levels, and
more.
And
we writers want to capture them. After all, the way a character speaks says a
lot about them.
But
aye, there’s the rub. Several rubs, in fact.
Hard to Replicate
Dialect
is hard to write and even harder to read and understand, especially in large
quantities. Have you ever tried to
write out a Bostonian’s accent? We all know “pahk the cah in Hahvahd Yahd,
Roberter,” right? Or that of someone from the Deep South? Y’all sho’ kin trah.
Or someone from The Bronx? Fuhgeddaboudit. You end up doing all sorts of
alphabetic gymnastics trying to capture sounds that are hard, if not impossible
to represent just with English’s 26 letters and a few punctuation marks. And
try to use all those special characters you find in dictionaries, the ones that
are supposed to help you understand how to pronounce a word? That’s asking a
reader to work way too hard. A writer might get away with that once. More than
that and the reader is likely to put the book down.
There
are better approaches. I’ll have suggestions on them later.
Disrespectful?
The
second rub is that some writers, teachers, and critics think writing in dialect
shows disrespect for characters, that it belittles them. There may be some
merit to this argument. Think about it: How many characters have you read, who
were supposed to have high cultural or economic standing, but spoke with a deep
southern accent or a slow western drawl if the story wasn’t set in one of those
locations? Not many, I’ll bet. That mismatch between how a reader expects a
character to sound and how they actually do could
make a character more interesting, but it could also be used to mark them in a
negative way.
If
a writer is creating this mismatch
intentionally, they need to make that clear as early as they can. Note,
however, that this might not be early at all if the author intends to misdirect
the reader, the other characters, or both.
Foreign
languages are also things to be careful with. If a character comes from a
foreign country, it’s OK in some circumstances for an author to drop in an occasional foreign word:
If it’s the right word, or the only word, she
can use to express a certain idea or concept;
If it’s a common-to-him word that he would
naturally use in place of the English one; or
Just to establish the character as being foreign.
It
can also be OK for an author to throw into a character’s dialogue enough
foreign words to show her putting on airs or otherwise trying to be someone she
is not.
Better
ways to show that a character is speaking English as a foreign language are to
use English words that are technically correct, or almost right, but are not
the ones a native speaker would use, or to rearrange the structure of their
sentences. Think about how Yoda spoke in the Star Wars movies, with his verbs at the end of his sentences.
Cover Other Weaknesses
A
third rub is an author using dialect, foreign words, or jargon to cover up
other weaknesses in the piece, particularly in characterization, or to show off
their own vocabulary. A friend of mine once used the word mephitic to describe
the smell of a men’s restroom. Sending readers to the dictionary is a good way
to ensure they never pick up the book or story again.
When Jargon is Acceptable
If
a character works in a field that has its own specialized jargon, which all do,
then it’s appropriate for him to use that language. Of course, the author needs
to use that jargon correctly, and in ways that would be natural for the
character. People often forget that others don’t understand their jargon, which
can lead to confusion and misunderstanding. Authors can and should take
advantage of that, so long as only the other characters are confused and not
the reader—at least not for long.
There’s
a special proviso here for non-fiction works: If the piece is being written for
a specialized audience (say for hunters and sport shooters in Guns and Ammo) or for a field’s
professional magazine (for example, Cell
in biology), then the jargon needs to be there. It adds clarity and accuracy
rather than reducing it.
The
general rule of thumb is that authors should use dialect, foreign words, and
jargon sparingly, only enough to establish what they need to about the character.
Once the character’s background, social standing, culture, heritage,
profession, etc., have been established, the author should minimize how much
they use those special words and phrases. If a character has been off-stage for
a while, using a little dialect or jargon when they come back into the story is
appropriate.
Questions for You
All
right, then, time to put on your reviewer’s hat. Here are some questions to ask
regarding dialect, foreign languages, and jargon as you review a work.
Is the dialect, foreign language, or jargon
necessary and appropriate to the piece?
If it isn’t necessary, appropriate, or both,
what should the author do to fix the problem?
Does the amount of dialect, foreign language, or
jargon, or the way it’s being written, make the piece hard to read? Does it
confuse rather than clarify?
If so, what should the author change or remove?
Does the author seem to be using dialect,
foreign language, or jargon to belittle a character?
Is that appropriate for the story? For example, does
he want the reader to not respect that character?
Could that be accomplished some other way, such
as through the character’s behavior? Is that being done already?
If none of these are the case, what should the
author do to fix the problem?
Does the author seem to be using dialect,
foreign language, or jargon to cover up other weaknesses or over-impress with her
vocabulary?
Used
properly, dialect, foreign words, or jargon can add to a piece, giving it the
flavor of a particular environment, giving a character an added or necessary
dimension, or adding a degree of authenticity or authority to the story. That’s
what you, as a reviewer, should be trying to help the author achieve.
What
do you look for, and look out for, when reviewing how an author uses dialect,
foreign terms, or jargon? Y’all kin ‘splain yore thinkin’ in that comment box
down yonder.
It’s
been longer than I care to admit since I worked on my third book, Wild Spread, in any serious way. There
are plenty of excuses for why, and some actual reasons, but neither change the
fact that work came to a dead stop. There was no flow—of words, of ideas, of
anything except frustration.
This
seems to be my pattern: intense periods of work followed by months of
inactivity. This time I was in a deep funk over the quality of draft 2 and the
inadequacies of draft 2B. And I wasn’t sure draft 3 was headed in a direction
that was any better. When that happens, stubbornly moving forward is just a
waste of time and mental energy. A writer friend insists that “all writing is
good writing,” even when it’s crap because it is writing, but I know myself well enough to know that at times
like this that’s a bad approach.
The
time away has allowed me to finally see where the flaws in the outline for the
middle of the book were and what they were. And I can thank writer Karen
Walker, a presenter at the recent Tucson Festival of Books and author of The Dreamers, a novel that also deals
with a world-wide plague, for giving me the idea for a fresh approach.
Walker’s
book has two story-lines, which she wrote independently, then blended. While Wild Spread has five major characters,
each of whom has their own story-line, my heroine, Janet Hogan, is supposed to
be the central one. Therein lay the problem with the outline (and maybe with
Act I of the book too): too much of the other characters, too little of Janet.
So
this week I’ve been thinking and writing notes about the plot as it relates to,
and drives, Janet, about what has to happen to her, and about she might act and
react. My job is to be as mean to her as possible—without being so crazy that my readers will throw the
book across the room—while giving her the opportunity in the end to overcome
everything I throw at her. Or not. (No spoilers here!)
So
now I’m close to the point where I can focus on writing Janet’s story, and from
that build the story-lines of the other characters to weave in. Some weaving
will have to happen from the start, as the characters have become so interconnected
through the first two books, but by putting my focus on Janet, the proper roles
of the other characters should develop naturally.
Should.
They could, of course, get stubborn. Characters do that sometimes. When they
do, I need to pay attention because they’re trying to tell me something, but
that too offers a way forward. And when I have an idea what that way is, I’ll be
back in the flow again.
Friendly Fire, by Scott A. Snook. Copyright 2000 by Princeton University Press
As
I did when I reviewed Joan Piper’s book, A
Chain of Events, I need to begin with a set of disclaimers.
I am a retired Air Force officer.
I was a Mission Crew Commander (MCC) on the E-3
Airborne Warning and Control System (AWACS) aircraft.
On the date of the shoot-down of the two Blackhawk
helicopters over northern Iraq—April 14, 1994—I was deployed to Riyadh, Saudi
Arabia, to fly missions enforcing the southern no-fly zone over Iraq for
Operation Southern Watch/Desert Calm, the counterpart to Operation Provide
Comfort (OPC).
In July 1994, when the first investigation
report was released, I was deployed to Incirlik Air Base, Turkey, to fly OPC
missions. I was in the audience at the base theater when the report was briefed
to the aircrews there the evening before it was released to the public.
I knew slightly both of the MCCs who were on the
AWACS crew the day of the shoot-down, and have since gotten to know one of the
senior officers involved in the decisions on who to prosecute or not. I did not
know the one AWACS officer who was ultimately court-martialed but declared not
guilty by the jury.
Because
this book was my second one on the shootdown, I was prepared for another
difficult read. I also came to the book with a fair degree of skepticism. The
author, Scott Snook, was an Army officer: what biases was he going to bring to
the work? I had skimmed the book before I actually sat down with it and was
concerned that, as a psychological study, it was going to be dry and
uninformative.
I’m
pleased to say that, on the first count, I think Snook did a fairly good job,
although hardly a perfect one. More on that in a moment. On the second count,
Snook’s in-depth and cross-level evaluation of the events, non-events, and
individual, group, and organizational psychology of what happened was far
better than I expected.
Snook introduces a number of concepts that are both
challenging and revealing. The first is the idea of the “normal accident”—that
in a complex system, which Operation Provide Comfort certainly was, with many
moving parts that were not as tightly linked to each other as all of the
players thought they were—some kind
of accident of this magnitude is almost certain to happen if the operation goes
on long enough. This might be, at first, a shocking and disturbing assertion,
yet on deeper inspection, it reflects something that we understand intuitively:
the more complex a device or situation is, the more likely it is that something
will eventually fail.
The
second concept Snook introduces is “practical action.” Practical, as used here,
means “as in practice.” In other words, OPC began with an extensive set of
rules and procedures, written down in dozens of different documents. Over time,
however, the people having to implement those rules and procedures found them to
be impractical, and so they created local rules and procedures that made
sense—were “practical”—in their specific situation. Whether they made sense to
the larger organization is another matter, one that the local practitioners did
not have the perspective to be able to judge.
Over
time, this movement to “practical action” led to Snook’s third concept,
“practical drift,” in which more and more formal rules and procedures are replaced
by locally-developed practical actions. Unfortunately, no one at any level, had
the ability to see all of the changes that had occurred, until they culminated
in two helicopters being shot down and 26 people dying: a “normal” accident.
Snook
reveals how the actions at the individual level of the two F-15 pilots who
fired the deadly missiles, the AWACS crew members who did nothing that could
have stopped them, and the OPC leadership who was unaware of the brewing
problems were practical and sensible to each at that moment. Unfortunately, they
were also wrong.
But
then Snook goes on to reveal how analyzing just the actions of these
individuals or groups in isolation is not sufficient to understand how the
shootdown occurred. It is also necessary to look at the interactions between
the individuals, groups, and organizational levels, not just in those few
tragic moments, but over the full three years of the life of OPC to that point,
to gain a full understanding of what went wrong and why. In this way, this book
is even more disturbing than Piper’s book. While Piper’s account of the
struggles of the victims’ families to understand what had happened and why is
deeply personal and emotional, Snook’s account is more chilling because of the
inevitability of something happening
during the course of the operation.
Perhaps
Snook’s most disturbing conclusion, however, is that in complex organizations,
when something goes badly wrong, it’s not possible to place blame in one location
or on one individual because so many people and parts share in it: blame can’t be
placed anywhere because it lies everywhere.
This
is especially disturbing for the families of the victims. Piper’s book is, in
many ways, a search for the one true villain, the one person on whom all blame could
be laid. Ultimately, the Air Force, the Department of Defense, the General
Accountability Office, and Congressional committees all failed to find that one
person. The F-15 pilots were not criminally charged, and the one AWACS officer
who was court martialed was found not guilty.
As
I read the book, I wondered if Mrs. Piper or any of the other family members
had read it, and if it in any way would provide, if not solace, at least an
explanation they could accept. Only one family member, the father of one of the
Blackhawk pilots left reviews on Amazon and Goodreads, and he was worse than
unsatisfied, going so far as to accuse Snook of lying. Sad as it is, this
outcome is not surprising.
The
book is not without its faults. It is rife with errors regarding Air Force
operations, which Snook and his civilian editor at Princeton University Press
likely did not even know were errors. To identify just two, a photograph
identified as being of two F-15s actually shows two F-5s, and a later
photograph shows the wrong model of F-15. Surely correct photographs were
available. Second, Snook asserts that all
of the AWACS crewmembers had the opportunity to intervene to stop the
shootdown, even though two of the teams on the jet—the technicians and flight
crew—had neither the situational awareness, the responsibility, the training,
nor the equipment to do so.
Finally,
I felt Snook went easy on the Army personnel at Eagle Flight, the operation
flying the Blackhawk helicopters. To be fair, however, I must note that they
were at several disadvantages: their base was far away from the one where the
rest of the operation was headquartered, and the leadership of the flight was
too junior (Captains or Majors) to have had the kind of influence necessary to
have forced their operations to be properly integrated into the larger force.
Those leaders evidently did not get the kind of support they needed from their
superiors. Blaming this failure on interservice rivalry, however, is an easy
way out, and I was disappointed to see Snook take it.
On
balance, this book does a great service to the field of organizational psychology.
Deep analyses of such tragedies are rare, in part because, as Snook himself
notes, few have such a wealth of records and investigational material available
to be analyzed. I can only hope that in the nearly 25 years since this tragic
event, the Army, Air Force, and other military services, and other organizations,
have learned the right lessons from this study: that “practical drift” from
established procedures is inevitable, and that few operators and leaders will
be aware of the drift under normal circumstances. Intense, multi-level
vigilance is required if there is to be any hope of preventing, or at least
reducing the magnitude of the “normal accidents” that are bound to occur.
Highly recommended.
Yesterday
I did something I have not done in ages:
submitted a short story to a science fiction magazine. The story, however, was
not mine: it was my late friend Cappy Hanson’s last work, “The Otter’s Stone.”
A few days before she died, she told me which magazine she intended to send it
to first, so that was where it went. There’s no guarantee the magazine will
accept it, so I’m not going to name it.
Submitting
a work, whether to a magazine, a contest, a literary agent, or an editor at a
publishing house is an action that readers are blissfully unaware of, but one fraught
with tension for the author. There’s no reason why readers should be aware, of
course, but for the author it’s a major milestone.
The
first step on the road to publication is, naturally, writing the piece. That
first draft almost always stinks. Ernest Hemingway himself supposedly said, “All
first drafts are shit.” For new writers, this is a tough thing to accept. Every
word is pure gold, isn’t it? When the response is, “Um… well, no,” it can be
quite a blow. But many edits later, there’s a poem, a story, an article, or a
book that might, just might, be worthy
of publication.
Then there’s the process of finding an appropriate market.
Sometimes that’s easy and obvious, other times not so much. The new or naïve author
may pick just one, sure that their work is perfect
for that publication. Maybe it will be. Maybe it won’t. There’s only one way to
find out, and that’s to send it in.
Oh,
but clicking that Submit button can be so hard. What if they don’t like it?
What if there’s one typo too many? Like ONE? What if…? What if…? Suddenly, the
writer’s imagination runs wild.
When
I submitted “Stone,” the magazine’s web site reported that there were 133
submissions ahead of it in the queue, that the average response time was 4 days,
but that I shouldn’t query them until 90 days had passed. Huh? These things
seem contradictory, but they’re not.
While
the submission was addressed to the magazine’s editor, he won’t see the work
right away, if ever. Instead, there are an unknown number of “slush pile”
readers, and one of them will see the story first.
This
is where things get dicey. Great stories get rejected all the time at this stage.
Maybe the first page of the story just doesn’t grab the reader. Maybe they’re
tired. Maybe they had a fight with their girl- or boyfriend or spouse and they’re
in a bad mood. Maybe they’re sick. Maybe it’s not immediately obvious why or
how this piece is right for this market. Maybe it isn’t right at all. Agents
and editors, if pressed, will admit that they reject pieces left and right,
every day. In the book publishing business, if the query letter doesn’t connect
with them, they never even see the manuscript, not even the first page.
Image courtesy of Chaiwat / FreeDigitalPhotos.net
Rejected.
Next.
With
short stories, the process is similar but there’s no query letter, only the story.
And
that’s how an average response time of four days is possible, even with a stack
of 130 stories.
If
it seems like a cruel, arbitrary business, well, it is. Even assuming the
author has picked the “right” target for their work, and that work isn’t just
the best they could make it, but is truly top notch, that story-cream may not
rise to the top.
But
let’s say the piece does make it
through the first round. It’s home free, right?
Oh,
no. There will be still more rounds of reviews, and at any point along that road,
the story could be shown the exit ramp. That’s why I was told not to query the
magazine until 90 days have passed. Chances are that I will hear something.
Chances are that the news will be a “thanks but no thanks” note.
And
then it’ll be on to the next market… and the next… and the next. Eventually,
maybe, someone will say yes, will want to publish the story. Maybe they’ll even
send a payment check. There are some publications that pay only in “contributor’s
copies,” or even just the satisfaction of seeing your name and your work
published there.
In
my totally biased opinion, “The Otter’s Stone” deserves more than a thank you
note and a byline. But I don’t get to make that call.
Two
weeks ago today, as I write this, my closest friend left all of us behind, going
on to whatever, if anything, is next. She left behind a lot of broken hearts
and fond memories. Fortunately, because she was a wonderful writer of poetry
and prose, a painter, a musician, and much more, we will have tangible things
to hold near to revive those memories.
Cappy
Cappy
left “too soon,” of course. Far earlier than any of us would have wished.
Frankly, we would have wished that she would never leave and spare us that
pain. Never mind that if we were the
ones to leave first, we would be inflicting that pain of leaving on her.
Such
is the nature of our feelings about those we hold most dear, even at times when
letting go is the kindest thing to do. I do not think that was the case this time, but what do I know?
But
of course, we all leave sooner or later. For some, sooner is too soon, for others
perhaps, later could not come soon enough. Sometimes, that’s all a matter of
perspective and perception, of the details of the relationship, how we
interacted with the other. One person’s mortal enemy could be another’s closest
friend, with both feelings being true within their context.
I
can’t—or won’t—imagine Cappy having enemies, or being one. Her heart was too
big, too kind, to full of love freely given, although truth be told, we never
know all of a person, no matter how intimate the relationship is. Still, no, I
won’t accept those other possibilities.
At
times like these it’s natural to reflect on mortality generally and on our own
specifically. What have we done? What is still to be done? What’s truly important
and what’s not: the products of daily life, or the contributions to the life we
wish to be known for? Sometimes, maybe often, it’s impossible to tell which is
which.
Our
legacy, in the end, is not just made up of a few big things—who decides what’s
“big” and what’s not?—but of the myriad small things we do day in and day out.
The kindnesses and meannesses, the gifts given and taken, offered and withheld.
Each is like a tiny spot of light or dark paint dabbed on a larger canvas.
Individually they don’t seem to contribute much, but when we step back, they
combine or cancel to contribute to, or even create, the overall tone and color
of the work.
Like
the painter, we’re too close to our work to truly judge it. Yes, of course, we
make our own assessment of it—we’re doing that all the time, whether we know it
or not; at times like these we do
know—and maybe we decide to make changes. Or decide not to. Or make no
decision, which is a decision itself.
No
matter what we decide, or don’t decide, those around us will make their
judgments about our decisions and what kind of a person we are.
On
a wall in my office I have a collection of wry, sometimes snarky “laws” of
human behavior. One is called Chisholm’s Law of Human Interaction. It reads,
“Purposes, as understood by the purposer, will be judged otherwise by others.”
In life, those “others” are everyone around us: friends, colleagues, casual
acquaintances, competitors, enemies, even people with whom we’ll only ever have
one single, fleeting contact. They’ll all judge, just as we do, Jesus’s reminder,
“Judge not, and ye shall not be judged,” notwithstanding.
So
when we reach the end of our days, when the string plays out and Atropos wields
her dread scissors, how we will be remembered is largely out of our hands. We
can only do the best we can, taking lessons from those who leave before us, in
the hope that we have done enough that when it’s our turn to leave friends
behind, their thoughts of us will be fond, their words about us kind.
It’s hard to say I “enjoyed” this book. After all, how
can one “enjoy” a book about the real murder of an eight year old girl by her
mother’s boyfriend? Indeed, at times there were tears in my eyes.
That said, there’s a lot to like—or maybe “appreciate”
is a better word—about Too Close to Home.
Let me set the scene first.
Cover design and photo by Jesaro Photography. Used with permission.
Samantha’s home life was anything but easy. Her mother,
Rachel Stra, had been divorced by Samantha’s biological father. Samantha and
Rachel had moved with Rachel’s boyfriend from Florida to western New York to
“get a fresh start.”
Angel Colon, the boyfriend, was no angel. He’d been
involved in drugs and crime in Florida and Georgia, and was abusive with Rachel
and Samantha. Despite that, he and Rachel had had two more daughters together,
but Samantha became the odd girl out in the family. To top it off, Rachel was
not the best of mothers: inattentive almost to the point of neglect.
Then one day in February of 1997, Samantha didn’t show
up for school, although Angel claimed he’d put her on the bus that morning. She
didn’t come home that night, and her classmates reported they hadn’t seen her.
The search began. By the time a week had passed,
suspicion began to focus on Angel and the possibility that Samantha was no
longer alive.
Stephen Tarbell was a “technical sergeant” in the
Wyoming County Sheriff’s Office (WCSO), and was involved in the case from Day
1. His co-author, Laurinda Wallace, is a native of the area who writes cozy
mysteries. Tarbell and Wallace had been acquainted for years, and when Tarbell
decided that he needed to write the story of the investigation, he turned to
Wallace for help.
Together they turned what could have been a dry,
Sergeant Joe Friday-like “just the facts, ma’am” report into a gripping and
often heart-breaking story. The authors do not just detail the myriad of tasks
and procedures the WCSO, the FBI, the New York State Police, and many other law
enforcement agencies and laboratories had to undertake, they tell the very
human story of men and women committed, to the point of endangering their own
health, to finding Samantha and then her killer.
There are, of course, plenty of details. When
Samantha’s body is found, almost exactly three months after she disappeared and
only 300 yards from her home, Tarbell and Wallace explain why it took hours to
exhume the body from its shallow grave, how the dirt above and around her was
painstakingly sifted for any potential pieces of evidence, and how bags were
placed around her hands to preserve any evidence that might be there. But at
the same time, they show how the discovery just added further motivation to the
heart-broken officers to find her killer and bring him to justice.
For me, one of the more interesting elements of the
story was not just how the various law enforcement agencies worked together,
but how, as prosecutors and defense teams came into the picture, a professional
and respectful relationship developed between all of them. It’s easy to assume
that police officers would view defense attorneys with suspicion, yet that did
not happen here.
The respect was mutual. Indeed, at the very end of the
book, after Colon pleads guilty to second-degree murder and is sentenced to 25
years to life, Tarbell and his colleagues end up at the same restaurant as the
attorneys from the New York State Capital Defenders Team. When the officers go
over to talk with the attorneys, it’s the attorneys who say, “Good job, guys.”
Wallace has said this was the hardest book she’s ever
had to write, and it’s easy to see why. But in so doing, she and Tarbell
powerfully showed how there are human beings behind their badges, real men and
women who will work themselves to exhaustion or worse on a case they care
about.
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
X Pixel enables businesses to track user interactions and optimize ad performance on the X platform effectively.
This cookie is set by X to identify and track the website visitor. Registers if a users is signed in the X platform and collects information about ad preferences.
2 years
personalization_id
Unique value with which users can be identified by X. Collected information is used to be personalize X services, including X trends, stories, ads and suggestions.
2 years
external_referer
Our Website uses X buttons to allow our visitors to follow our promotional X feeds, and sometimes embed feeds on our Website.