I stopped by Side Salad‘s employer’s Web site to see if his co-workers provided any blogworthy offenses. Found something on the first try, just like the last time I tried this. Maybe I’m just too picky, but this annoys me:
TAMPA – A 59-year-old man threatens his mother and a health-care worker with kitchen knives, throwing one at a Pinellas County deputy’s head while being pelted with capsules of powdered pepper spray.
A day before, a 27-year-old man driving a stolen utility truck drags a Pinellas deputy’s patrol car beneath a boat trailer, ignoring commands to pull over.
Sunday, a 41-year-old man tries to burn down his home, threatens suicide and points a plastic-and-metal tool that resembles a gun at a Hillsborough County deputy at an RV park.
Monday, a 20-year-old man suspected of delivering rock cocaine tries to run over a Tampa police officer with a pickup truck, and then leads police on a 20-minute chase after being shot in the chest.
The lede was an acceptable (if a tad overused) example of present-tense storytelling; the ensuing graphs set me off: “a day before…” puts the sentence in past tense. Same thing for the next two sentences. Mixing present and past in the same sentence is not a crime against humanity or anything; it’s just ungainly, and unnecessary.
A bulleted list, with the past-tense stuff as bold-faced lead-ins, would’ve been a handy quick fix. It’d need a quicky intro preparing the reader for the list, then something like this:
- Monday: A 59-year-old man threatens his mother …
- Sunday: A 41-year-old man tries to burn down his home.
- April 22: A 20-year-old man suspected of delivering rock cocaine tries to run over a Tampa police officer…
This makes the lead-in more like a headline, and lets the present-tense stuff stand on its own — preserving the writer’s intentions while assuaging my need for order in the universe.
There is, of course, another whole issue with this lede technique: It’s a second-day story illustrating how/why police shootings happen. If you bullet three items you’re four inches into your story before you get to the “what it all means” part. If you’re on the rim and you pick up this story, the first thought in your head must be “will the nutgraf appear before the jump?” If it doesn’t, you’ve got a battle on your hands because somebody’s gonna have to change something they don’t want to change. The sooner you get that over with, the sooner you can set time aside for more essential matters like reading somebody’s blog.
Definitions for non-newsies: “nutgraf” is what we call a sentence which explains why this story is running in today’s paper. Ideally this would happen in the opening paragraph (the “lede” if you haven’t caught on to that by now), but reporters often have other ideas and we indulge them to keep them on the job (more on this below).
The “jump” is the point where it says “story continued on Page x.”
Designers often build pages with no regard for where the nutgraf appears in the story (sometimes they don’t know, sometimes they don’t care), and we don’t want to force readers to turn to an inside page to figure out why they’re reading the story. So: if the nutgraf is several paragraphs down into a story and falls beyond the jump point, either the story or the design will have to change. Usually it’s the story because it’s the easiest fix — changing the design affects all the other stories on the page, and all their jump pages too.
Reporters generally have no clue to these complexities; all they know is the result: the desk is forcing them to redo something they considered done. It’s one of the reasons why reporter morale is usually worse than copy editor morale, even though they’re getting more pay and all the glory. One of the reasons many reporters become editors: it’s more fun doing it to somebody else than having it done to you.