Peevish Pen

Ruminations on reading, writing, rural living, retirement—and sometimes cats. And maybe a border collie.

© 2006-2012 All rights reserved

My Photo
Name:
Location: Rural Virginia, United States

I'm a retired teacher turned writer. Ferradiddledumday (my Appalachian version of the Rumpelstiltskin story) and Stuck (my middle grade paranormal novel) are available from Cedar Creek Publishing.

Monday, March 19, 2012

Signs of Spring

Spring came early this year—before winter was gone, the weather turned unseasonably warm, the grass turned green, and the flowers bloomed. Here are the signs of spring in my neighborhood:

Garden shoes, garden gloves

Forsythias at Polecat Creek Farm


Wild plums along the road.

Dogwood tree almost ready to bloom

A recently shed antler

Redbud trees by the driveway

Buds on the pin oak

Gazebo

Tulips

Violets

Luminaria

Jim-Bob the kitty

Cherry tree

Corkscrew willow & cherry tree

Farmland & Jack's Mountain

Melody grazing in a green pasture.
~

Labels:

Saturday, March 17, 2012

Drop-Out

Warning: Boring health stuff that you might want to skip.

I dropped out of the diabetes mangement class I signed up for last month, even though I had two classes to go. Why? The info I was getting wasn't helping me manage my diabetes.

I'd hoped to learn more about the glycemic index, glycemic load, recipes that don't cause my BGs to soar, some new developments in treatments or research, a list of helpful books, etc. I wanted to know which diabetic diets worked and which didn't—and why. I was really hoping for some research-based techniques to lower my BGs (blood glucose, or blood sugar).

Mainly I wanted to bring down my HbA1C level. Also called the A1C, this blood test shows your average blood glucose levels (EAG) over the last two or three months. Under 6 is normal. I scored 10 on February 1st. Not good. As you can see on the chart below, a 10 means that my average BGs were 240. Not good at all.


Anyhow, the "diabetes management" class was about how we should eat according to the USDA food pyramid. I already knew that the food pyramid was more political than it was helpful and—despite its acceptance by the American Diabetes Association— that its heavy reliance on carbohydrates (the energy source that diabetics can't process!) was downright dangerous. There's a history of the food pyramid at http://www.healthy-eating-politics.com/usda-food-pyramid.html.

I think this part is interesting (bolding mine): ". . . the American Heart Association . . . was proposing that fat and cholesterol consumption should be lowered for better heart health, even though the link between the two had never been proven in any scientific study. With this focus, the creation of today's USDA Food Pyramid began."

If you lower fat intake, you have to increase the other two sources of energy—carbs and protein. The instructors of the diabetes management class didn't seem to get that diabetics can't process carbs very well.  They kept stressing lowering dietary fat. On the third session about eating according to the food pyramid, I asked when we'd be looking at other ways of eating. Answer: We're sticking to the food pyramid. (The special allegedly diabetic-friendly snack we were served that day—one ingredient was low-fat cream cheese—shot my BGs up to 178.)

No way can a diabetic process that many grains!

The last class session I attended was devoted to reading food lables. Not a discussion of what those strange ingredients were in some processed foods and how they affected people, but how to compare carbs to fat to help us eat low-fat. Aaarrrggg! That's why I didn't return for the last two sessions. I'd wasted enough time. Doing more of what doesn't work won't make it work any better.

My health history (you might want to skip this): In 1994, I was diagnosed with "fibromyalgia," most likely to explain why I was still achey and fatigued after my 22 months of chronic mono had abated. I was a mostly-vegetarian then: For nearly two decades, I'd eaten lots of pasta, rice, whole grains, potatoes, etc., and not much fat or protein. I was pretty much eating according to the food pyramid's recommendations—and in those two decades I gained about eighty pounds. 

During those decades, I lived in a neighbor where "lawn care" companies spewed toxic stuff over many of the lawns around me—albeit not mine. In a one-block area, two women died of breast cancer, one man contracted lymphoma and eventually died from it, and there were a couple of heart attacks.  I had a series of strep infections, a bout with chronic mono, and "fibroymalgia." In the early 90s, I lost two dogs to diabetes and a cat to cancer. Looking back, I think my fatigue, brain fog, and aches were diabetes symptoms, but I wasn't declared diabetic until 1999 when my gynocologist thought I was diabetic. He was right. My other doctors hadn't bothered to test. After all, "fibromyalgia" covered anything that was wrong with me.

After being diagnosed diabetic in early 1999,  I read Dr. Bernstein's Diabetic Solutions and started low-carbing, I noticed that not only did my blood glucose levels drop substantially, but my fibromalgia symptoms nearly vanished. I dropped over forty pounds in six months. However, the aches, brain fog, and fatigue would return with a vengeance if I ate too many carbs—particularly bread.

Through the years, however, I fell off the low-carb train a couple of times because my blood glucose levels were so far down that I surely figured I could eat like a regular person again. But I couldn't. If I ate what non-diabetics ate, my blood glucose and weight soared again. When I went out to dinner or attended a party and partook of forbidden foods, I'd spend the next two days recovering from the aches and fatigue of my carb hangover.

For the last seven weeks—since cutting my carb intake way back (less than fifty grams a day) and giving up wheat, my fibromalgia-type aches are gone again. I don't limp or have bad leg cramps. My blood glucose levels are coming down (now they average 160, which is a little below an A1C of 7.5). I've lost 13 pounds. My acid reflux is gone. I think more clearly. I have considerably more stamina. None of this would have happened if I'd followed the "diabetes management"class directions and eaten the food pyramid way.

I know from re-reading Bernstein's book, reading Wheat Belly by Wm. Davis, MD, and reading Good Calories, Bad Calories and  Why We Get Fat by Gary Taubes, that the food pyramid way of eating—which promotes low fat and high carbs—is dangerous for diabetics. If you're diabetic, I recommend reading those books. Too bad the folks who designed the diabetes management class hadn't read those books. I'd have loved to discuss them in a class.

If you're hooked on the ASDA food pyramid and low-fat, you might want to read Gary Taubes'  22-page New York Times article, "What If It's All Been a Big, Fat Lie." If you didn't watch Wm. Davis's videos that I posted on my February 29 "Wheat Belly" post, you might like to watch them. And if you read one of the many articles that declares low-fat is the way to eat, look to see if the article references a clinical study.

The Atkins pyramid is one example of the kind of food pyramid that diabetics should use:


It's kind of like flipping the ADA pyramid upside down and putting diabetic-friendly foods at the bottom..

Some more interesting reading about low-fat diets:
http://www.mindbodyhealth.com/lowfatdietmyth.htm
http://www.survivediabetes.com/lowfat.html
http://www.phlaunt.com/diabetes/19066498.php
http://diabetesupdate.blogspot.com/2011/06/news-you-missed-whi-low-fat-diet.html

I wish the folks who designed the diabetes management class had read the above articles. Meanwhile, I'll manage on my own.
~



Thursday, March 15, 2012

Found Hound Update

For a few days, I'd taken around fliers, asked local folks, contacted fox hunts within a 75-mile radius, and posted on FB and elsewhere on the Internet about the hound who showed up here Sunday. Nona Nelson of the Roanoke Times posted about him on her "Happy Wag" blog. But no owner came forth.




But—from the master of hounds at the Sedgefield Hunt in North Carolina—I did learn that he's a Walker hound who likely competes in field trials (hence, the number on his sides). Well, I'd tried Googling field trials and didn't have any luck.


Jason from down the road came by to look at the hound. He has beagles but knows a lot of hound folk. He told me that field trials weren't held on this side of Rt. 29. And he told me the numbers are applied with a stencil and hair dye.


I emailed my animal communicator friend, Karen Wrigley, who said "he felt like a working dog who ran off the beaten track from everyone else. With my back to the front of your house I want to turn my head 1/2 way between my front and the left shoulder. I think he came from that direction."


Karen also said, "He may have come from out of town. . . . He wants to be with his other dog friends . . . but it seems sooo far away. I think they are looking for him because he feels them thinking of him."   


About the time I was replying to Karen's email, I got a phone call from my neighbor, Mitzi Cabeen of the Smith Mountain Hounds. She'd been the first person I called when the hound showed up Sunday. Turns out she encountered a numbered hound on the road over her way, and the hound wanted into her truck. She took the hound home with her. But that hound's number was F1. Could what I thought was a number 5 be the letter F? Good possibility!


Somehow, through a person who knew a person who knew a person, Mitzi tracked down a guy in Blairs (54 miles away) who'd sold some Walker hounds last fall—numbered and with tracking collars. The guy who'd bought them wanted them as deer dogs. The one at Mitzi's didn't have a collar either, but he had a dirty square on his neck that indicated he'd worn a tracking collar not too long ago. Did the hound at my place have such a mark?


I went out and checked. Yep. He did.


Long story short: Lance Fowler, whose father and uncle breed and train hounds 54 miles away, came out to look at the dogs. The F on the dogs' sides stood for Fowler. She showed him a picture of the hound I'd found. It had been one of theirs, too. 


Why these hounds were collarless and running loose, we don't know. Did the purchaser dump them after hunting season was over? It's a mystery.


Anyhow, Mitzi called and said they were coming over. Soon Mitzi's car appeared in my driveway. Behind it was a red truck hauling a dog that looked almost exactly like the one I'd found.



The one I had was called "Mayday." He knew his name and he appeared to know the boys.



Anyhow, "Mayday" was reunited with his buddy.





There they go.



If the guy who'd purchased them comes looking for them, we can direct him where to go.

Meanwhile, there's another hound somewhere out there who needs to be found. While the Smith Mountain Hounds were fox-hunting in Pittsylvania  County last weekend, one of Mitzi's pack didn't return when the others did. So, if you happen to find a red and white male foxhound. . . .

Labels: ,

Monday, March 12, 2012

Found Hound

Update, Wednesday, March 14: The hound, whose name is Mayday, was picked up by the breeder's family along with a pack-mate who'd found a friend of mine. Stay tuned for a post about this.

Yesterday, we found a hound. Actually, the hound found us.
Today, we impounded the hound in our kennel.


The nice-looking hound is an un-neutered male. He might be  a Walker or a foxhound—some hound breed with long legs. He's sweet and personable, respectful of cats, good around a horse, doesn't seem interested in cows, and he has numbers on his sides. One side looks like it might be a 518 or a 513.


The other side looks like it might be a 612, but I'm not sure. He might have been numbered because he was in some sort of competition.


Last evening, he really wanted in our kennel, but Maggie—who micro-manages the kennel—wasn't keen on that idea. He'd tried to get into a neighbor's kennel that morning. This morning he was outside the garage door. He followed me around and I gave him a modest breakfast. Oddly, he doesn't eat dry food, only canned food.

Today, my husband got him into the kennel without incident. He went to sleep in the grass. Below, Maggie tries to show him the finer points of digging a rat-hole, but he isn't interested.


Harley the Catahoula shows him around . . . 


. . . and watches while he naps.


He dozes off while Hubert the elderly beagle watches.


Hubert decides a nap sounds like a good idea.


If this is your hound, or you know who he belongs to, let me know by clicking here.


I think this hound really wants to go home. When he walked with me to the paperbox this morning, he looked intently at every truck that went by.
~


Labels: ,

Saturday, March 10, 2012

Laying Bricks

A few weeks ago, I decided that the stepping stones to the gazebo weren't enough for a decent walkway. Luckily, we had some leftover bricks down at the farm that I could recycle. After we trucked them to the gazebo, I dumped them and thought about how'd I'd arrange them.


I know nothing about bricklaying, other that the ground should be flat (it mostly was) and I should have some kind of pattern so the bricks would fit. I raked back the mulch, removed the stepping stones, and figured out a pattern for the bricks as I went along.


Before long, I had what might pass for a brick walkway. 


It's a little shaky, but I figure eventually the bricks will settle. Since I'll be the main user, it's good enough for my purpose. Plus, I can always pull up the bricks and rearrange them if the walkway gets wobblier. Right now it looks mostly OK—not great, but it'll do.


I've been in enough writing groups to know that a lot of first-time writers are like this first-time bricklayer. They get an idea, put the words down quickly without having a definite plan, and think their first draft is the finished product. Odds are good it's not. The plot might not have a definite pattern, the characterizations might be a little wobbly, or the dialogue might be a bit shaky.

Maybe revising a manuscript is like pulling up bricks and realigning them. 
~

Labels: ,

Wednesday, March 07, 2012

Upgrade Woes

Here we go again. I decided to update the iMac to Snow Leopard.


I was a little hesitant because of what happened with my iBooka few years ago, but I popped in the disk and the upgrade started.

Long-time readers might recall that in November 2009, I ported all the stuff on the iMac (with Leopard operating system) over to a new iBook (with Snow Leopard OS), but I had a big problem with fonts not displaying correctly. I blogged about it here ("Leopard & Snow Leopard & Word, Oh My!") and here ("The MacBook Woes Continue"), and how an advanced Apple tech rep named Tammy finally fixed the problem here ("The Woes Done Gone").

After today's installation was complete, the message said the install was successful. But the same font problem happened again today. I called Apple. I'd thought my warranty on the iMac didn't expire until mid-March, but it had actually expired a couple of weeks ago, so the nice tech guy couldn't help me unless I paid a fee. However, he suggested I try to fix the problem myself by going into the font book and validating fonts. So that's what I did—and I did find several fonts that were corrupted. However, that didn't fix the problem: documents in both Word and Pages looked like crap, and the documents wouldn't print.

Here are two examples of how bad the font problem is. I used Times New Roman for both. The first was written in Pages, the native word processor for Apple. Besides the spacing problems, the punctuation was badly messed up:

Word was better, but not by much. 


The printers don't work for most fonts, but a few fonts that I don't normally use look OK and will print. So, looks like I'll have to call Apple again. And pay a fee to upgrade this upgrade.

Oh, woe.
~

Edited on March 10 to add: On Friday afternoon, Apple support tech David M. fixed the font problem in a bit less than two hours. I had to download a temporary program that enabled him to see my iMac and then he walked me through how to fix it. I didn't have to pay a fee because Snow Leopard has free 90-day tech support.

Labels:

Monday, March 05, 2012

Morning (with Cows)

We were supposed to get snow in the wee hours of this morning—anywhere from a dusting to maybe an inch. We didn't. Here's how the sky looked when I walked down the driveway to get the morning paper.


Nary a snow cloud in sight. A flock of grackles flew by and some lit in the oak tree. You can barely see them in the top left of the photo below, but you won't see any snow because there wasn't any:


Across the road, a pregnant mama cow nursed her last year's baby.


Another cow stopped grazing to watch me. Maybe this cow was babysitting the calves behind her.


The bull wandered by to see what I'm doing. What I was doing wass not getting too close to him.


While the herd lined up to graze in an orderly fashion, the cow who watched me earlier checked me out again.


And again.


Eventually the herd moved away from the fence.


And I moved on, too. A few snowflakes fell while I was taking the cow pictures, but barely enough to notice. I guess the snow moved on somewhere else.
~

Labels:

Sunday, March 04, 2012

Forever

How could I have taught English for so many years and not read Judy Blume's Forever?


Recently, however, I finally got around to reading this 1975 novel, written before young adult books were even called YA. Forever, which won the 1996 Margaret A. Edwards Award,  has gone through several editions. Obviously Forever is a popular book to have lasted so long. What's it about? (Warning: Spoiler Alert)

Katherine ("Kath") and Michael, two seniors at separate high schools in New Jersey, meet at a New Year's Eve party. Soon they're dating and getting serious. Yep—eventually they have s*x (which Kath, the narrator, is pretty explicit about), but not until after they've vowed to love each other forever. And they're careful and responsible. However, their forever love unravels after Kath—at her parents' insistence—goes to work as a tennis instructor at a summer camp and Michael goes to work at a relative's lumberyard in North Carolina. Kath, despite her forever love for Michael, finds a fellow counselor attractive. After Kath's grandfather dies, the fellow counselor comforts her. When Michael arrives unexpectedly at camp to see Kath, an argument ensues, and—well—you can guess the rest. Their love isn't forever after all.


The novel was pretty edgy in the 70s. Now, it's just kind of sweet. Kath's parents are still in love with each other, and Kath gets along with her 12-year-old sister. Kath's mother is supportive but not intrusive; for instance, she provides Kath with an article about teenage sexuality which gives Kath something to think about. Kath puts off having sex with Michael because she's "not ready." When they do have a relationship, they're responsible—he uses a condom; she visits a Margaret Sanger clinic in New York to get the pill.


Since Forever was written so long ago—Kath would now be the same age as the target readerships' grandmothers!—it's very dated. Hence, no smartphones, no Skype, no Facebook or other social media, no texting or even emailing. They listen to records, not iPods. Michael calls Kath on her family's landline and she takes the call upstairs to have some privacy. Since they go to separate schools, they only see each other on weekends. When she's in Vermont and he's in North Carolina, they correspond via snail mail. 

Would girls today be able to relate to the lack of instant access? I don't know. They could probably relate, though, to Kath's feelings and emotions, her difficult choices, and perhaps her acceptance of responsibility. Some things don't change.

Despite being  somewhat dated, Forever is an excellent book for a mother to discuss with her teenage daughter. The novel is explicit, however, and some parents might have problems with Kath's descriptions of what she and Michael do. In fact, Forever ranks #7 on the American Library Association's 100 most frequently challenged books for 1990-1999 but drops to #16 for the 2000-2009 list. Even after all these years, lot of folks apparently want to see it banned from school libraries and public libraries. 

In a letter to "Friends at Sugarloaf School," who had apparently made Blume aware of a controversy about Forever, Blume says in part:

. . . Forever is sexually explicit, but it deals with emotions and responsibilities. You can't go back to holding hands, as Katherine's mother says in the book, so you'd better think ahead. I wrote the book with a young teenage audience in mind. When kids ask how old they should be before reading it, I urge them to wait until they are at least twelve and then to take their questions to a caring adult. But I've had letters from kids even younger who say they read and understood every word in the book - and letters from older teens who started it, didn't feel ready, and put it down. Kids don't read books that make them feel uncomfortable.  
When one adult or group of adults demands the removal of a book from a school or library, those adults are making a statement to the students. This book has something in it we don't want you to know about. We don't want to deal with this subject. We don't want to answer your questions. Your questions make us uncomfortable. Calling it smut, as someone recently did in the Citizen's Voice, only makes kids more anxious to read it, and leaves them thinking they can't ever go their parents with questions. As a parent, you can tell your child you don't want him/her to read a book. What you can't do is make that decision for all parents and their children. I encourage parents to use Forever as a bridge to communication, to use Katherine and Michael to help them talk about topics they may not have discussed before. If their values are different from Katherine's and her family's, fine. They can tell their children what's right for their family and why.  
What matters is that young people continue to have a choice in reading materials. What may not be right for one parent's child may be exactly right for another's. Imagine if we pulled every book from the school library that presents ideas and situations we may not agree with ourselves! Instead, if we learn to talk to our kids, listen to what they have to say, and learn to trust them, we won't have to worry about the books they choose to read. 

On her website, Judy Blume has this to say about censorship. And on this page, she tells why she wrote Forever

I'm glad I finally got around to reading Forever. I wish I had recommended it years ago to some students of mine when they were struggling with difficult choices.
~


Labels: