Lessons Learned

Hello, Again

I haven’t written in a long long time. Isn’t that always the story, though. Unless you have a habit, an identity, or a following, it’s really hard to make a site like this, a blog really, worth it. And I haven’t got any of those things. I don’t know who I’m writing for, and I don’t know why I’m writing. But I’m paying for this site anyway, so I guess I might as well write something.

It’s been a year – or two. Back in August 2021, I changed jobs. I was really happy where I was at. I had been working at HireVue. I’d been a data engineer there, and a staff software engineer. I had (I think) respect, and I was doing a killer job with work that I loved to do.

Then, in – oh, I don’t remember – I think March, maybe April, of that year, Facebook knocked on my door. I’d just had a coworker leave to go to Facebook, and it felt like everyone around me was leaving, and I thought, “well, why not give it a shot?”

So, over the course of two or so months, I interviewed, prepped, fretted, all the things you do for a FAANG job, and lo and behold, I landed a job! I was on vacation when I found out. The pay was, well, amazing. I mean, it wasn’t as good as I’d been told during interviews, but it was still really really good. And the offer included relocation, which was a boon for me and my family at the time, because we’d already been looking to move.

Together with my family, we packed up, moved quick, and by August, we were living in Snohomish, Washington, and I was working – largely remotely – for Facebook, soon to be Meta.

I was a data engineer. I worked in the Infrastructure organization. And the job was nothing like I expected. All (well, most of) my interviews had been really technical. But I spent a ton of time in meetings, talking, managing projects, and just trying to figure out what the heck needed be done. I didn’t love it.

As a technologist, I love to get my hands dirty. I love to be wrapped in code. Give me a really tough problem, let me go to work, leave me alone, and I’ll come back in a day or two, or maybe a week if the problem is truly challenging, with some awesome code, a really great solution, and I’ll feel energized, I’ll love it. But stick me in a room, just listening to people talk; make me fight and work and manage and toil to do everything to get people to listen and to move a project forward. Do that, and I’m going to be exhausted and demoralized.

It’s not that I can’t do it. In fact, I do it really well, and that’s one of the things that creates problems for me. It’s hard to find people who are great technically, but who can also convey complex ideas to business folk, and who have experience managing projects and programs. I’m one of ’em. And so, inevitably, I get pulled into that kind of work because employers need people who can do it. But I hate it. I just wanna code. I love being in the tech.

Meta just wasn’t that for me. I tried. I really did. But after a year, nothing was changing, and I was unhappy. And so, I put my ear to the ground, and listened for opportunities outside of Meta. An old friend from my HireVue days came calling with an opportunity at his current company, eVisit. I knew a few folks that jumped ship from HireVue to eVisit, and I thought I’d interview.

Interviews went well, and they really wanted me, but I balked at first. I was still trying to make a go of it at Meta. And I had another potential offer at a non-profit that I was really interested in. So, I turned down the initial offer and moved on.

But after a few more months of fighting to make Meta work (fruitlessly), I decided I needed to leave for my own, as well as my family’s, health and sanity. Coincidentally, eVisit reached back out to see if I’d reconsider. I was still trepidatious. It’s hard going from a multi-billion, big-name, well-established tech company to a small start-up, but I thought, why not? Besides, I’d be able to get my hands dirty with tech again. So, I said yes.

I’ve been at eVisit for two months now. I’m the sole data engineer. There’s a ton of work to do, and a lot of opportunity to transform the data environment. As much as my time at Meta drained me, I still learned and experienced a lot, and I saw what possibilities are out there with respect to data. Even though Meta’s data environment is extremely proprietary, there were lessons to learn, and I hope I can apply at least some of what I learned from Meta to my work at eVisit.

We’ll see. The company is small. They’ve had some success, and I hope they’ll have more in the future. Creating a truly data-driven culture and implementing the tech behind it doesn’t happen overnight. I hope I have the chance to make it a reality.

Maybe, just maybe, I’ll keep this site posted with my progress.

Lessons Learned, management, positive

Forcing Functions

I’m glad I committed to write weekly on this blog. During the week, I don’t think about it much, if at all. I might ask myself whether some experience or thought I’ve had is worth blogging about, but that’s the extent of it. When the weekend comes, though, the knowledge of my commitment drives me to write something, anything to keep the commitment.

This is a “forcing function.” It’s a constraint I’ve put in place that compels me to act in a certain way. I’ve also committed to being positive on this blog. That forces me to filter my activities and thoughts during the week through a lens of positivity. This is useful because it’s easy to fall into a pattern of negativity when I’m surrounded by it in the news and on the Internet.

In journaling this morning, I thought more about forcing functions. What other forcing functions could I introduce in my life? I don’t think they need to be huge. I’ve noticed, for example, that there are things I avoid doing at work because they would be forcing functions that might drive me in ways I don’t want to go, or steal away some of my “freedom.”

For example, at work, I try to avoid saying what I’m going to do. Instead, I do it, and report it later. This is a way to avoid committing to something I’ll later be held accountable to deliver. It seemed like a good idea when I developed this habit, and it may have merit in some situations. But I think it has downsides, too.

Stating my intent to do something is like making a little promise. And because I value my status amongst my peers, that little promise becomes a forcing function that drives me to action. Add to that a deadline and it will drive me to deliver faster. It doesn’t have to be a big bold statement. A simple statement like, “Let me take a look at that and get back to you later today,” is enough to do the trick.

This is a habit that can be tremendously useful in helping me achieve my goals. I don’t need to state my intent about everything I’m planning to do. If I save those statements for actions that will push me in the direction of goals, then they will have the advantage of compelling me to move in the direction I want to go.

That’ll be a focus for me in the weeks ahead at work, and maybe even outside work, too. Making this statement here is a perfect example. Having made it, I’ve made a commitment, and I already feel compelled to act on it. Here’s hoping it pays off…

Lessons Learned

Starting Anew

Is this experience familiar? You decide you need to start keeping a journal again. You open up your journal and begin writing. “It’s been too long since I last wrote,” you begin. You continue with a quick catch up of where you are in life. You comment on your desire to improve. And you commit to keeping a journal regularly.

As you finish, you leaf back through the pages to see when you last wrote. It was more than a year ago. Here’s what you said, “It’s been too long since I last wrote…,” And you closed that entry with a promise to keep a regular journal.

Journaling is a habit, and – like any habit – it takes concentrated effort to form at first. It’s a habit that I don’t have. Though, it’s a habit I’d like to establish.

I started this blog several years ago to fill a requirement in a business class. Each week, I was given a prompt to address here, in this blog. I’ve tried to bury those early posts because they no longer fully reflect who I am or what my priorities are. This being the Internet, I’m sure they’re recoverable.

As the class that prompted this blog came to its end, so did my regular upkeep of it. That’s a shame. I pay for the domain. And I think there’s some value to having a “vanity” domain to stamp something of my own mark on the Internet.

In the intervening years, I’ve tried to write here now and then. I’ve tried to establish some identity for this blog. But my efforts have been spurious at best.

The challenge, I think, is that I’ve always tried to scope the blog to some particular purpose or identity. And when I do that, I recognize two things. First, nobody really knows this blog exists. It’s public, so of course people can find it, but they’re not gonna find it unless they’re looking for it. Second, given my inconsistency, virtually any subject I might write on is almost certainly covered more thoroughly and reliably elsewhere.

But I need to create. I need a place to put my thoughts down. I want to have some identity beyond the circle of my close friends and associates. And so, against my own doubt that it will actually go anywhere, I will give this all another shot. And here’s what I plan to do.

Rather than try to tailor my site and my writing to one particular purpose, I’m going to make this more of a traditional blog or journal. In nearly every week of my life, there is at least one day, one hour, or one moment when I have a thought or opinion or experience that I think I’d like to share with others. That’s what I’ll do here. I will strive to write something every week, reflecting on my week, and capturing that opinion or experience I want to share.

Could I write more frequently? Sure. And maybe I will. But my only commitment at this point is to write once a week. Will my thoughts coalesce around a particular topic? Maybe. But that’s not my goal. My goal is simply consistency.

My hope is that, as I write consistently, there will be certain topics or ideas that become natural focuses for my writing. When, and if, there are, then I may spin those off into their own separate sections for this site, or I may redefine this site in terms of those topics. For now, though, consistent writing about my weekly thoughts and experiences is what I am committed to deliver.

Here goes nothing…