Friday, February 23, 2024

What's In a Name?

 Friends, 

 

This weekend we will continue our Lenten series, “Between Our Rock and Hard Places,” by focusing on two Scriptural texts where names are changed. As a way of focusing, the Community Engagement Commission put together a collection of questions that speak to our theme this week. The first few questions are, “What’s in a name? Where did my surname originate? Has it been changed over time? Where did my given name originate?” as well as, “How do my names really name me?

 

I’ll start the process by reflecting on my names, the origins of which sound biblical, but that may be as a much of an accident as anything else. The Welsh surname “Davis” is a derivative from “Davidson” which originally started out as “David’s Son.” I don’t know if there was a “David” whose son was declaimed as “Davidson” along the way, or whether it was an attempt by pietistic ancestors to locate themselves in the family of King David. Likewise, the name “Mark” has obvious biblical connotations and was one of the most popular names throughout the Roman Empire during New Testament times, since it is derived from Mars, the god of war. I was not named after either the gospel or the god. My mom told me that Mark was the name of a cute guy on a soap opera that she liked, so she gave it to me. (I missed my call to be melodramatic eye candy.) 

 

Some of my family names evolved slightly (Smythe to Smith, Adamson to Adams, etc.), but as far as I know none of them was changed because immigration officials couldn’t pronounce them, or to accommodate the prevailing WASP culture to which my families emigrated. When we ask, “What’s in a name,” we want to be sensitive to those whose names have been marred by inept officials, anglicized in order to mask ethnicity, or changed in other ways in order to “fit in.” We also want to be sensitive to those who have chosen to change their name. Some feel the need to distance themselves from a namesake, others change their name because they were assigned a gender at birth that does not fit their identity, and others change their name to reclaim a lost attachment. The question, “What’s in a name?” has many layers of stories.

 

The other questions that we developed for this week move toward the names that we receive along the way such as, “Do I have a nickname? Have I ever been called names that were unkind? Those kinds of questions can rake up pleasant or unpleasant memories, perhaps some of both. Nicknames can sometimes be endearing, but often are meant to tease someone’s physical features, abilities, or mannerisms. They may offer us a chance to live into, reject, endure, or ignore them, as far as we have a say in the matter. 

 

The final question we developed will be addressed explicitly in this week’s Scripture readings, “What is God’s name for me?” The short answer to that question is what we heard in the baptism story last week: “Beloved.” That’s your name. You are God’s beloved child. No one can take that away from you and trusting in that name can bring tremendous comfort and strength when we are tested. I hope you hear that often, if not in your own mind, at least when we speak to one another at St. Mark. In life and in death, you are God’s Beloved Child, because nothing imaginable can separate us from the love of God in Christ Jesus. 

 

We will read two stories this week when God and Jesus give names. God renames Abram and Sarai, then Jesus renames Peter. The contrast between these two stories will show that naming not only has the capacity to lift up the lowly, it is also a powerful way of bringing down the haughty, by making something plain and bringing into words what might otherwise be hidden. In Peter’s case, it will be a moment of difficult truth. Oh, Simon Peter, bless his heart. And God be with those of us who find ourselves more like him than not. 

 

That’s a teaser, folks! See you in worship this weekend. And plan to stay for a while after worship for our Town Hall meeting featuring our Deacons! They are up to lots of good. 

 

Mark of St. Mark

No comments:

Post a Comment