Why I read Hawthorne

I’ve been thinking about this post for a while, putting it off because I couldn’t remember my professor’s name, and it made me sad. The things that are so important to us at certain times in our lives can be difficult to hold onto. It’s like another world, another Sam that existed, and I don’t always share her memories.

Which is, ironically, a fantastic segue into what I’ve been thinking about – American Romanticism. Or, more specifically, American Dark Romanticism (or American Gothic) of the early to late 1800s. Mmmmhmm. I can feel your excitement right now.

I fell in love with this particular literary movement in high school, when I first read The Scarlet Letter. And don’t come to me with “ugh, that book is so boring,” because then I’m convinced you didn’t read it.

My adoration grew in college, when I was pleased to take two classes with a professor (the aforementioned one whose name has escaped me, and I feel like I’ve betrayed my degree) who shared my excitement over this time period. He taught a class in Crime, Morality, and Punishment in 19th and 20th Century Literature, and if that doesn’t sound like a whirlwind of a time, then I don’t really know what is. And he taught early American Lit. AKA all of the quietly, sneakily depraved writing of the 1800s.

When most people think of gothic literature, they think of Poe and his Raven. I love Poe, too. One of my favorite assignments in college was my feminist critique of The Fall of the House of Usher. I had a grand time with that. Not to mention “A Descent Into the Maelstrom,” a view into that human nature to hang a foot off the edge of a cliff, to see what might happen.

But the dark romanticism of the age, for me, is settled snugly in the hands of Hawthorne. I find myself thinking about his writing a lot lately. As the world has shifted underneath me, and I feel unsteady, I think about the Minister’s Black Veil or Ethan Brand. I imagine him sitting and writing the words, his cautionary tales about the world, about Us vs. Them, about false piety.

He wrote extensively about Puritans. His grandfather had been a judge during the Salem witch trials, after all. He did not cast them in a favorable light. They are instead depicted harshly, like deep, rough lines against an otherwise normal backdrop. They are hypocritical, placing their chosen heroes on pedestals and denouncing their preferred outcasts. And inevitably the heroes are flawed, and the outcasts are noble (though also flawed because they are human).

It strikes a little close to home these days.

Think about what you may (or may not) remember about The Scarlet Letter. Spoilers, I guess? But then again, this story is over a hundred years old. You’ve had ample time.

Hester Prynne has been put in jail, unwed (or, more specifically, widowed) and now with child. They cannot put her to death, so they instead require her to wear a scarlet letter A upon her clothes, forever marking her sin and displaying it for the world to see. They demand to know the identity of the father, but she refused. She lives outside of the village, raising her daughter.

Hester otherwise lives by all of the puritanical rules of society. She wears somber colors, is gentile and respectful. She also sews the most elaborate and beautiful dresses. Her daughter wears fanciful and colorful outfits, and the wealthier matrons in the village hire her for all manner of seamstress work. She tends to the sick, staying by their beds to comfort them. But still she is treated as an outsider, an untouchable.

The local minister, Arthur Dimmesdale, is meanwhile looked on as a paragon of society. His increasingly poor health is attributed to his piety, with many members of his church believing that he is fasting, or that he is simply so overwhelmed with goodness that he is being called to Heaven.

It is, instead, his own guilt eating away at him.

At the end of the novel, before a crowd of people, Dimmesdale rips away his shirt, confessing that he is Pearl’s father and that his sin is all the greater for having allowed Hester to bear the burden for those 7 years. The crowd is stunned to see a bright scarlet A branded on his chest.

(Yeah, see, boring my ass.)

The village immediately turns on him, some shouting that he should be hanged for his sin.

Until Pearl, the child of Hester and Arthur’s union, speaks out, reminding all in the crowd that they, too, have sinned. That in the wake of seven years of her mother’s continued service to the town, she has heard some say kind words. That her father has been seen as holy and admirable. She reminds them that forgiveness is more important than judgment.

I could talk about (or write about) this story for hours, for days. Hawthorne so brilliantly captures the hypocrisy of those shouting about propriety. And in this modern era of loud voices and pulpit-pounding, I find peace in these tales.

Dimmesdale dies after his confession. He and Hester do not run off the Europe to start a fresh life together and they had hoped a mere chapter earlier. But Chillingworth (just read the story, seriously) finds forgiveness, and he leaves his fortune to Pearl a few years later. When Hester dies, she is buried by Arthur. Though he feared they would be damned together, Hester believed they would be forgiven and spend an eternity by each other’s sides.

And I guess that’s why I love Hawthorne. Though dark and at times depressing, the background characters of his tales often learned a lesson via the suffering of his protagonists. He did not sugar coat his stories; he shed light on the harsh truths of society but still maintained hope that people could learn and grow and change.

I need that reminder.

Of course, there’s always Poe, too. When it’s time to simply scream into the void. That might work just as well.

Disappointment

In the immortal words of The Rolling Stones, “you can’t always get what you want.”

There are some days I feel the statement should be amended to “you seldom get what you want” (and apparently, so did they. Looking at you, “Satisfaction”…), but then that’s not really the point of the song.

In every day use, we just stop there.

“I had hoped to do X, but it didn’t work out.”

“Well, you can’t always get what you want.”

“Gee, thanks for that insight.”

We forget about the second part of it. “If you try sometimes, you just might find, you get what you need.” And frankly what we need isn’t always what we want. I want to smother my face in melted chocolate and eat pizza all day, every day. But my body needs “vitamins” and “nutrients,” so I eat sensibly. Most of the time.

Of course the reason we don’t complete the sentiment is because disappointment sucks. It’s a shallow victory to hear “well, this didn’t go the way you wanted, but it’ll work out in the end.”

Yeah, the end was supposed to be successfully obtaining X. Now it’s…what? Unknown. Unknowable. Until you’re some days, weeks, or months beyond, and you look back to see the worn path behind you, and that light clicks on. Ohhhhh.

Sure that part is satisfying. I like to retrace my steps, counting them and watching the twisting way that they got me to where I am standing now.

But right now now it sucks. It just does. There is no sugar coating it. There is no “well, everything happens for a reason.” No. It just sucks.

Still, you know, in the scheme of things. I get it. My disappointment, on the world’s scale of sheer craptastic things, this is like….in the thousands. High thousands. I know that. I really get it. There are people out there who can’t even rely on the second part of that lyric because they’re not very likely to get what they need either.

I keep telling myself that, when I take a breath, and for whatever reason, the air I’ve breathed in seems to just carry all of the things that I’m even slightly bitter about. I keep telling myself that, when the little, nagging things that don’t usually bother me suddenly snowball, and I’m just running frantically from the avalanche. That’s right, running. I’m not about to face a giant snowball of little nagging things. Frankly, if I wasn’t dealing with them when they were tiny, why would I deal with them when they’ve become so big? No, thank you.

And I guess by now, you’re wondering where I’m going with this.

I’m not really sure. Haven’t gotten there, yet.

Sorry to disappoint.

 

Georgia on my mind

I grew up in the peach state, various towns and cities at different times, only vaguely aware that people lived in other states. It’s weird how that happens. When you define a place as Home, it feels strange sometimes to think that there are billions of people out there who not only don’t live near you, but have most likely never even heard of your town.

When I was very little, I affected a thick Southern drawl, drew out my syllables as folk do in Georgia. But over time that dwindled, even living in the state. People who meet me now will not often guess that I spent the better part of my pre-adult years (and even early adult) in the foothills of Appalachia.

Fun fact: Georgia is the largest state East of the Mississippi. Yes, it’s true. Yes, even when you take the Upper Peninsula into consideration for Michigan.

I mention that because when I tell people I grew up in Georgia, they almost always know someone in Augusta or Savannah. I lived about 6 hours from them, in that case. I most likely don’t know them.

I’m headed that way on Saturday, the hubby and I hopping in a rental car to make the drive down. We’ll spend some time with my family at the homestead in the hills, and then I’m dragging him along with me to Southeast Dreamin’.

SED-Web-Logo-e1453762337688

In addition to being excited about being in the place I learned how to walk and speak and be an adult*, I’m really excited about this stuff:

  1. Charlie Isaacs‘s keynote. He’s one of my favorite people in the community, so I’m very happy to see him speak.
  2. Rebe de la Paz is going to talk about educating end users – a topic near and dear to my heart.
  3. For my NPO friends, you can check out Adam Kramer‘s session on Optimizing NPSP as an Admin.
  4. My friend and fellow #GifSquad member, Amy Oplinger, is reprising her fantastic session on Imposter Syndrome.
  5. Phillip Southern is going to share how they created the open-source Trailhead leaderboard.
  6. Doug Ayers is sharing his presentation on using Process Builder to create a Chatter Bot.
  7. THE Jen Lee of Automation Hour fame is sharing a session on Flow.
  8. Chris Duarte‘s closing keynote! It’s like a delicious Salesforce sandwich, people.

Did I mention the Hackathon on Thursday (this will be my first!)?

Did I mention the SaaSie Tech Social?

Did I mention time with the community, seeing the #Ohana?

To be honest, Georgia hasn’t been home in almost 10 years, but having so many great things to look forward to, I know it’ll feel a lot more like it next week.

See you there?

*I am legally an adult. Whether or not I’m an “Adult” is up for debate.

 

Hear me []

A friend of mine, the amazing @SalesforceAmy, gathered a group of us women in the Salesforce #Ohana with a great idea that she and another amazing woman, Rachel Rogers, had for celebrating International Women’s Day (which is today, by the way). I’ve been thinking about how I could contribute – video? Picture? Retweet machine? And then I remembered that I have this thing called a blog and generally speaking, I write about things…

I’m not the most vocal person, unless I really know someone. So the hashtag #hearmeroar seemed disingenuous to me. You won’t hear me roar because that’s not really my style. But you might read my words.

I carry a small notebook with me wherever I go. I have 4 small black notebooks all filled, cover to cover, and dated. Their pages contain my triumphs and, more often than not, my defeats. They are my roar.

My roar is the long line of strong women in my life. My maternal grandmother who moved herself and her two children from the tiny island nation of Malta to New York City. My paternal grandmother, who has lived up to every challenge that the world has thrown at her and continues to learn and do amazing things. My mom – holy shit, my mother…smart, funny, driven, thoughtful, kind, brave…the list goes on. I am in awe of her every single day.

My roar is the list of things I have done that surprised even myself. Finished 3rd in my class at the fire academy. Moved across the country and somehow turned my life around. Taught myself math, so I could teach math in a struggling school district. Became a Salesforce consultant. (What is my life?)

Sometimes my roar is just getting through the tough times.

Sometimes it’s leaving a company because they show a pattern of disrespect to the women who work there.

Other times it’s supporting another woman who is going through something I’ve experienced.

For all of us, though, our roar is the collective will to continue pushing forward, the defiance in the face of systems that tell us that we are at fault for being born as women, our ability to keep standing when we’ve been pushed down. Our roar is in our strength – a strength that does not need to boast or strut, a strength that persists, that permeates everything that we do. Our roar is collective, and it shakes foundations, and if that scares some people, then it’s only because they thought that we were kittens, when in fact we are titans.

So you will not hear me roar today. You may never hear me roar.

But you will hear me.

You will hear all of us. Because we will not be silent, and we will not be silenced.

Today is International Women’s Day. Here’s to our voices.

 

The niche struggle is real

There are so many smart people in the Salesforce Ohana. Seriously. So many. They are in the community, on Twitter, writing blogs, hosting podcasts, just generally being awesome. Need to know how to write a formula? There’s a blog for that. Process Builder trouble? There’s a weekly webcast for that. Prepping for an exam? So many sites to help.

As someone who has always been the person on the edge of social circles, one foot in and just hesitant enough to not insert myself, I can tell you that it can be hard to find your place in any situation. As someone who likes to write, who feels safest being herself behind a keyboard, I can also tell you that it’s not any easier finding your place via the blogosphere.

When I first started with Salesforce, blogs helped me become a better admin. I used Salesforce’s documentation to learn the functionality, but project and product management, understanding users’ needs, best practices…that all came from the community. Once I started feeling more confident, I wanted to share what I had learned with others. I’ve tried a few avenues – speaking at events, starting the local Women in Tech chapter, evangelizing on the streets, you name it. Oh yeah. And this thing you’re reading.

I have a backlog of drafts about a mile long. Posts I’ve started, trying to fit into my own little corner of the Salesforce blog world. Am I a place for new admins to learn basic functionality? Am I a marketing automation guru? Maybe I should talk about consulting? Women in Tech. Community. Automation. Communication. Learning to code. Etc. Etc.

Guess what? It exists already.

There are days I find it disheartening. I don’t have the experience or knowledge that many of the existing bloggers have. It’s easy to be down on myself, to feel inadequate, to think that this whole thing is a waste of time.

Not what it’s about, though.

If you want to share something or do something or create something in this community, I’m giving you the permission and the advice to do it. Even if it’s already been done. Even if you think no one will care. All of those blogs and MVPs and community heroes didn’t become experts overnight. They all started somewhere, and they are all here to support you.

Oh, and if you’re looking for your niche, your expertise? It’s you. It’s your unique perspective, your own experiences. That’s all you need. So you’re basically half way there.

 

It’s Official: Sales Cloud Consultant

I bit the bullet last Saturday and took the Sales Cloud Consultant exam.

(She writes, as if she hadn’t been studying 1-2 hours per night for the past two months.)

I did the online proctoring, something I said I would not do again. But you know the saying about the best laid plans. It only took 10 minutes to get it set up this time. We’ll call it a win.

I thought about how I wanted to share this, if at all. My natural instinct is to provide some sort of guide, some insight to those that are considering taking it, preparing. There are already some great resources out there, though, and I’m not a fan of reinventing the wheel.

So instead I’m going to give you some honest feedback about what you can expect:

  1. Most people don’t pass this exam on the first try
  2. Your test-taking ability will come into play on this exam
  3. There is a LOT of information covered – both breadth and depth
  4. No matter what you study, there will be things you did not anticipate

I prepared for this exam for almost two months, starting with about an hour study each day and moving up to 2 hours each day a couple of weeks out.

I did what I always do. I downloaded the study guide, prioritized topics based on what I felt the least comfortable with, and I went to work. I used Salesforce’s existing documents, reviewed some Trailhead modules, inspected existing blog posts about Sales Cloud (shout out to Salesforce Ben!), and took copious notes. This method got me through both Advanced Admin and App Builder.

I guess technically it got me through Sales Cloud, too.

If you’re looking toward Sales Cloud on the horizon, here’s the best advice I can offer you: be patient with yourself and DON’T PANIC.

dontpanic

As I write this, I’m cool as a cucumber, ya dig? But literally five minutes before the exam, I could feel my heart trying to rip itself free from my chest. Taking these exams IS nerve-wracking. But guess what – it’s not the end of the world. All you can do is take a deep breath and focus on the question. Don’t worry about whether or not you’re going to answer the exact way Salesforce wants you to (because sometimes it’s really not clear). Worry instead about understanding the problem presented, understanding the potential solutions.

Having certifications is great. I love it. I love getting my name printed on paper.

But certifications aren’t going to make you a good consultant. Listening will. Empathy will. Curiosity will. A growth mindset and patience will. If you have those things, then you’ll do fine.

And, if you are taking the exam soon and somehow stumbled here, I hope you take a moment to breathe and relax. You’ve got this.

 

 

GTD Newb

I didn’t make a huge announcement, but those that know me probably already know that I made a change and joined the team at Arkus, Inc. So hooray for that.

//giphy.com/embed/WIg8P0VNpgH8Q

via GIPHY

One of the best things about starting with them is that they have a structured onboarding process, and it involves reading and implementing David Allen’s Getting Things Done methodology. GTD for the initiated.

I read the book before my official start date, and it was eye-opening. To quote one of the Arkus founders, “geeks love it.” I can confirm that. Anyway…I read the book, and me being me, I wanted to drop literally everything and implement it immediately.

That is not realistic during the holidays. There’s stuff to do. Hours in the car. Family gatherings. Festivities. New video games.

So instead I did the holidays thing, and then I did the starting a new job thing. GTD sat in the peripheral, staring at me, poking sometimes, even. I took on some of the “quick win” type things right away; I made lists of actions, had a list of projects, emptied my mind every couple of days. That alone made a difference.

This past weekend, I talked the husband into implementing GTD at home, and the entire weekend was focused on that implementation. We went through our upstairs home office, gathered all of the Stuff and then we processed it. We determined what our ongoing process will look like.

Can I be honest? This is my blog. I’m going to be honest. I don’t know if it’s going to be a stellar success at home. Not for any other reason than I’ve read the book, and the hubs hasn’t. Also he’s extremely action-oriented. He basically has been doing GTD for years, just…without calling it that.

Enter me, his wife, a whirlwind of paper and ideas and aimless, but still voiced and well-intentioned, goals that are forgotten as soon as they’re spoken aloud. Opposites attract.

Anyway.

Day 2 was me getting down into the nitty-gritty for the job things. I’m blessed because Arkus provided OmniFocus to me, the tool for Mac users that helps manage the GTD process. I captured Stuff; I created projects and assigned next actions; I set up some key commands. I am as a ready as I’m going to be. I even set up an action item, deferred to a month from now, to review my process and how I’m using it.

I’m excited.

I’m still new to all this, but I was talking to my mom this morning, and she said “you sound so less stressed. Even a month ago, you sounded so much more stressed out.”

And I really am.

There are a lot of reasons for that – good news about health of friends and family members, making some priority changes, the #ohana…and yeah, some of it really is because of this GTD thing.

It’s so weird for me to write that. You have to understand just how jaded I am about “life hacks” and planners and productivity and self-help and whatever. eyerollI’m the person that looks like RDJ when Cap proudly announces that he understood that reference.

I am not about to sit here and shout to everyone that they need to implement GTD because it changed my life. It has not changed my life. It is a new aspect of my life that is part of a greater change that has happened, and I enjoy it. It helps me; it makes sense to me. Frankly, so does Nerdforce’s great new admin leveling app idea! I can’t wait to build that and potentially expand on it.

Because it is becoming part of my life now, it’s going to pop up occasionally in this blog. If you are interested in GTD – what it is, trying it out, what-have-you – then feel free to search tags for it, go to the sources listed below, or reach out and ask. I will stumble through whatever answers I might have.

And in the meantime, I can cross this off of my action list. Done.

It feels later than it is

And I’m studying, but I keep staring at this empty page, “Person Accounts” written neatly and definitively at the top.

Person Accounts.

What a strange string of words to the uninitiated.

I had two client calls today, during which I attempted to pack everything I know about the Salesforce architecture into a neatly packaged, five-minute explanation. All to find out if I needed to configure a junction object.

I’m still not sure if I need to build that junction object.

So here I am, at my dining room table, just shy of 9pm, and I’m studying for my Sales Cloud exam (next Saturday. No pressure.). All I can think about is how strange Person Accounts sounds.

I should be studying, committing to memory the fact that, yes, you can flip the switch on Person Accounts (by contacting Salesforce and requesting it, of course, complete with business reason), that you treat a Person Account like a Contact, and I should be considering, as a Consultant, the option of simply creating a “Household” Account record type.

But instead I’m staring at the words. Not thinking. Just staring at them.

I write when I can’t think. Realistically, I just need to step away from a bit. Stop thinking of Leads, Contacts, Opportunities, custom objects, schema…Person Accounts.

It’s been a long week. Not bad. Just long. Did a lot of work, a lot of studying. I saw Hidden Figures (got a whole post about that coming…eventually). But it has been long.

So just a bit more. Just Person Accounts stands between me and the weekend and a few hours of quiet and maybe some Deus Ex.

Back to it, then.

Lessons Learned: Record Type IDs

Yeah. I forgot I started this series. I’m only human.

I remembered it when I was thinking about this story I’m about to share (names and places changed to protect the innocent), so here it is.

(BTW, I was inspired to write in this style by the creative work of my friends at Nerdforce!)

screen-shot-2017-01-17-at-4-20-31-pm

I’m a professional, see; I don’t configure big changes in Production. I do it in a sandbox, like the big shots.

The changes were easy – one record type that needed some minor adjusting. A field added here, another field removed, a picklist value added there. Some workflows. It was the kind of work that I had done hundreds of times before. I know how to write a formula, know about adding the picklist value to the record type.

The only hiccup? A validation rule that needed to fire for other record types but would’ve spelled bad news for users of this one.

But I’m not just any dame. I’m an Admin. I didn’t break the rule, but I bent it, making sure that my record type could slip in under the radar. I knew I wanted to be precise, so I added NOT(RecordTypeID = [long string of random numbers and letters]). It’s nothing I haven’t done before. It takes a lot more than record types to get under my skin nowadays.

And my client? Another satisfied customer.

After only two hours of work, I created my change set, pushed to production, and disappeared into the night.

Then things got quiet.

Too quiet.

Until my phone rang.

“Hello?”

“Admin! Thank Benioff! We’ve got a real problem brewing down here.”

“Oh, yeah, what’s that?”

“Well that record type, ya see, it’s workin’ great except that no one can save a record. There’s a problem. It’s flashing red, and it don’t look good, kid.”

Undeterred, I flipped open my trusty laptop, “Tell me what it’s saying.”

“It’s an error message. It wants us to give it a value in some field, but we ain’t got the picklist. It’s sayin’ it won’t give up the record without it. What are we gonna do?”

I had to think fast. I had tested that very validation rule. Playing it cool, I asked, “Are you getting this error every time?”

“No. We didn’t even know it knew about this record type. Should we just…give it what it wants?”

“Don’t do that. But give me a minute to think,” I assured the client.

Like the flash of a muzzle, the answer came to me. Yeah, I had done this before, but here I was, caught like a fly in the syrup. Like some two-bit beat admin with something to prove and nothing to back it up with.

The change set. I should have caught it sooner, should have known. It had been staring me in the face. But I had to make sure.

“Let me call you back,” I said.

I hung up and stared at the screen for a minute. So this was how I would be done in.

I opened the validation rule. There it was – that 18 digit code. 18 characters between me and solving this case. I knew the answer; I wasn’t stupid, but I had to look anyway. I opened the record type. Different ID. The switch had been made right under my nose.

I’m no fool, and no change set was gonna best me.

I copied that ID, replaced it in the validation rule and saved. Not about to look bad in front of my client, I tested the change. Purred like a kitty cat.

The ringing on the other end was shrill, like it was shouting the client’s concerns.

“Admin?”

“Yeah, it’s me,” I smirked, “and I solved the problem. You won’t be getting that error message again.”

I waited while they tested it, and I disappeared during the celebration. They would be fine, I knew.


So the moral of the story here should be pretty simple: don’t hardcode IDs in your formulas or validation rules in a sandbox. Because they will be different in production.

Understanding multi-tenant architecture (which I swear, I do!), it makes sense. You can’t have the same unique identifier in two separate orgs. That would create chaos. And a sandbox doesn’t get any special treatment.

So really, you have a few options here:

  1. Temporarily turn off the validation rule in sandbox and remember to update it in production.
  2. Make the change in sandbox and duplicate in production.
  3. Don’t use the ID – use the name. You can always change it later if need-be.
  4. Don’t ever use Record Types
  5. Don’t ever use Validation Ruls

Disclaimer: Numbers 4 and 5 are not actually options. 

Either way, something like this isn’t the end of the world. But it is definitely good to keep in mind, especially if pushing changes to production late at night or early in the morning when users are less likely to be active, but you’re caffeinated and raring to go.

Also…full disclosure: this has happened to me more than once. I hope that by sharing my story, I will actually keep myself from repeating my mistake.

Have you learned this same lesson? A similar one that involved using hard-coded IDs?

 

 

Resolve

If I haven’t mentioned it thousands of times before, I went to college to study writing. Both of my parents are writers, and I had big dreams of becoming the next Maxwell Perkins. Things worked out a little differently.

I haven’t lost my love for writing (she types in her blog), and I haven’t lost my love for language – all of it. Morphemes, phrases, clauses, tropes, schemes, diction. Nothing that I learned in college has proven to be useless; as a Salesforce consultant, I communicate a lot. Even were that not the case, I still enjoy it all.

For my senior seminar, we had to read The Professor and the Madman, which is a compelling tale about the history of the Oxford English Dictionary. Worth the read, even if you’re not big into that kind of thing. What set the OED apart from other dictionaries at the time was that it provided the spelling of words, the meaning, and the background of those words – when did it come into being? When did its meaning change, if ever? All fascinating things.

Taking that a step further, Bill Bryson wrote about the history of the English language in his book The Mother Tongue – another very good read, if you have the time (obviously you do, right?)

Words change over time, frequently because of changes in society. People start to use a word ironically or sarcastically, and the word changes. That’s the beauty and frustration of the English language.

It’s January now, and that means the time for resolutions. I read this blog post about New Years being a time to drop old commitments, rather than take on new ones, and it got me thinking about words. I thought about the word resolution, how it’s used to describe a way to solve a problem. Which made me consider the word resolve.

Resolve means to close an issue or come to conclusion, but it also means strength of will. Do you have resolve? How will we resolve this problem? I wondered how we, English speakers, came to the meaning.

Resolve entered the English language in the 14th century from the old French resolver or the Latin resolvere. The original meaning was to loosen or unyolk; it described freeing something or oneself, not shackling to something new. Through the typical indirect, winding way that this language tends to use, it came to be what it is now.

I haven’t made a real New Year’s resolution in years. It has always felt empty to me, like a silently understood and agreed upon thing in society – we all are meant to make resolutions, recognizing them as void contracts with ourselves. No one expects others to keep to their resolutions. I imagine the whole thing started with someone drunkenly proclaiming that this would be the year they changed things for themselves. Did that first resolution maker follow through?

So this idea of giving up something, rather than taking on more, led me to the etymology of the word resolve, and I find myself thinking that maybe all of this comes back full circle. What was old is now new again, right? It’s a common trope in literature, trying to recapture the glories of yesteryear.

This is where I make some grand statement amount refusing to make a resolution because of its emptiness, the void contract, instead proclaiming myself free of the burden. Eh. Why bother?

I have goals this year. 2016, while not my favorite year, was good to me professionally. I worked hard, and I reaped the benefits. I’m ready to do more. More certifications, more engagement, more…Salesforce, more Ohana.

But words can change. 100, 200…500 years from now, the words I use today might sound different, mean something else. But actions will always be the same. Helping someone, offering a hand, lending an ear – these things will never change the rewards, the sacrifice, the connection. So rather than shout to the rooftops or the servers about what I aim for this year, I will continue trying to do. To be.

Happy New Year