Review: Every Girl Gets Confused by Janice Thompson

Read Every Bride Needs a Groom First

Amazon Description

Katie Fisher and Brady James may be a match made in heaven, but that doesn't seem to guarantee them a happily ever after accompanied by angelic choirs. In fact, the sounds being heard at the bridal shop where she works are on the contentious side lately, as a bride- and groom-to-be try to mediate the growing rivalry between their basketball-obsessed families in the middle of play-off season. On top of that, Katie's parents are nagging her to get out of Dallas and come home to tiny Fairfield where her former boyfriend Carson is waiting for her, ready to rekindle their relationship. Oy vey! What's a girl to do? And will she ever be able to wear that gorgeous wedding dress she won?

My Review

This is the second novel in a series, and I probably would have enjoyed it more if I’d have read the first book, Every Bride Needs a Groom. There are two reasons for this: it appears the story carries straight on from the first book, and there are so many characters, I got confused more than once trying to remember who was who. Of course, now I’ve read Every Girl Gets Confused, there’s no need for me to read Every Bride Gets a Groom, because I’ve pretty much sussed out all the important things that happened.

No, Katie wasn’t the only one to get confused. Actually, the title in itself was confusing, because Katie a) wasn’t a bride, and b) wasn’t confused. In fact, she seemed to be the most unconfused person in the novel, as her major confusion was around why Brady wasn’t forward in telling her how he felt (clue: he’s a man, and while many fictional heroes are happy baring their hearts, Brady was more, well, human).

Every Bride Gets Confused was written in the first person, entirely from Katie’s point of view. This was both a strength and a weakness—while I enjoy novels written in first person, especially when they have plenty of humour, the weakness is we are never able to see what Brady is thinking. The other possible weakness is that Katie is a pretty together person and her voice doesn’t have as much humour as I’d expect in romantic comedy. However, there was still plenty of comedy, mostly from her family. There was also too much introspection from Katie at times, particularly in the beginning, and this made it hard for me to get into the story.

Once I got into the story I very much enjoyed it, and appreciated the understated spiritual truths. But the spiritual and life lessons were mostly lessons learned by Brady and the supporting characters, which made Katie feel more like the observer/narrator than the centre of the story. I came away feeling Katie is a person I’d like to have as a friend because she’s hard-working, stable and a strong Christian, but I never got the feeling she went through any major confusion or character change herself.

Overall, Every Bride Gets Confused was enjoyable, but not as good as Red Like Crimson, which I recently reviewed.

Thanks to Revell and NetGalley for providing a free ebook for review.

Review: Red Like Crimson by Janice Thompson

A Book with Antonyms in the Title

(I know red and crimson aren't exactly opposites, but they clash, and should never be seen together. That's why I'm counting this as a book with antonyms.)

Adrianne left college eight years ago when she found out she was pregnant because she didn’t want to destroy Chris’s calling to serve as a missionary in Central America. She now lives in Philadelphia, and is beyond surprised when Chris visits her workplace one day as a member of a wedding party. For his part, Chris is shocked but pleased to see Adrianne again, as he never understood why she left college with no warning, or ignored his letters (like, posted letters. So quaint).

The persistent difficulty of a secret baby plot is the secret. There has to be a good reason why the woman never told the man she was pregnant, because many readers will find it hard to like a heroine who deliberately keeps that kind of information from a man, especially if he’s a good and likeable man (which we hope he is, because we want to see the couple together by the end). We need to see the heroine make at least reasonable attempts to contact the father, or have some major yet believable reason why she doesn’t.

And this is getting harder and harder with smart phones, email and social media: most people, especially young and new adults, own a smart phone, have an email account (that doesn’t change address even if they do) and are on some kind of social media (e.g. Facebook, Instagram). This makes it less and less likely that a woman simply wouldn’t be able contact her baby’s father. Red and Crimson got around this by being set in the near past—I found at the end the story was written in 2007, and the lack of mobile phones and the mention of a digital camera made it feel that old (and isn’t it ridiculous that only eight years ago feels ‘old’?). Despite this, the writing was strong enough that I never questioned the lack of email or social media as I was reading.

I got the impression from the ongoing “never the groom” comments that Red and Crimson was part of a series—it felt as though I was supposed to know Chris, Stephen and some of the other characters. But the story stood alone, and I never felt as though I was missing valuable character history in order to understand Red and Crimson. Nor did I feel as though I was being dumped with information about minor characters (something I have come across in other novels).

The theme of the story was forgiveness: God has forgiven us our sins, so we need to forgive ourselves and move on into the life God has planned for us. It’s a message many of us have heard before, but a message that bears repeating. It also reinforces the truth that we are called to be missionaries wherever we are placed, that we don’t have to be in some far-off developing nation to serve God (and while the author doesn’t specifically say so, some people serve God from their homes by writing Christian fiction).

Overall, Red and Crimson was an enjoyable if quick read that Christian romance lovers should enjoy. It was a sweet story with a plenty of conflict but not so much that it felt over-the-top (unlike the last novel I read …). There were a couple of typos (like Adrianne and Adrienne in the book description!), but nothing which interfered with my enjoyment of the story.