A Fair Share of Goodbyes

To say that the past few weeks have been full of changes would be an understatement, and all of those changes have resulted in my having to say goodbye more often than I can remember in such a short period.

As I mentioned in my last post, I recently changed positions at my job and am now working in the RSA Security division of EMC.  This change in position was truly a blessing for me, and has provided me with a way to more easily support my family and prepare for our baby boy, who will be due in just a few short months.  My new role is a lot less stressful, and is right in line with my career path for which I got my degree.

But even though this was such a good move for me to make, it was still extremely difficult to leave the team that I’ve been working with for almost two years now.  This probably sounds strange because we’re all still in the same building, but within the different divisions there is a sort of culture, and I have grown very familiar with it and have gained friends from all over the globe from Boston to Australia to Ireland because of it.

It has also been difficult to transition from my last role as an escalation point.  In my last post I explained in detail—probably too much detail, I’m sure—what my previous position entailed.  I was what is referred to as a Subject Matter Expert, or SME, which means that I was an escalation point and mentor for a specific technology called Fully Automated Storage Tiering, or FAST.  After another colleague from Utah and I became SMEs, our two mentors in Boston moved up the corporate ladder and we became the primary escalation points.  Because of how busy the work was, their positions were never backfilled, and although I was able to teach a few training courses on the subject, nobody else were ever raised to SME status.

When I “gave my two weeks,” I agreed to remain in my old seat for some extra time to act solely as a mentor and trainer.  During that time, I wrote training articles and PowerPoint presentations, built out a Support Wiki with tutorials on troubleshooting FAST cases, and worked with my team to help them take and work cases in which I specialized.

But there eventually came the time where we went our separate ways.  Because EMC leased additional space in our building, most of the divisions changed their locations in the building and my old team moved upstairs to the new area.  The RSA team, who was at that time on the 3^rd floor, moved down to the area adjacent to where I had been sitting since I was hired.

Even though the physical move itself wasn’t too bad, it was surprisingly very hard to say goodbye to my old team.  Many of them have become some of my closest friends, and it was hard to think that I wouldn’t be able to sit and chat in person with them while I worked each day.  Again, I’m surprised at how hard it was because they are now only a floor away, and I am still able to go up to their area to assist every now and again, and with our company’s instant messaging setup we are still to chat with each other any time.

I am also pleased to say that my new team is really great as well, and in the short time that I have worked with them I have already really grown to like them and know that it will be exciting to work with them.  They are very knowledgeable but also very down to earth and humble when working with me, and are not condescending in any way that I am newer to the ball game.  My new manager is also incredible.  She was my manager in my old division until she moved over to RSA about six months ago, and has been so kind to me.  She has been very close with me and has made sure to keep updated on our baby’s progress and is so excited for us.  She even gave us a wedding present when I got married!

However, this leads me to other goodbyes that came about.  As part of accepting my new job, I was required to fly out to Reston, Virginia, for two weeks to be trained on the product that I will be supporting.  My manager decided that it would be best for me to go in January so that I would be back with plenty of time for the baby to be born.  It would also be easier to go this month than wait until we have a new baby that I would also have to leave behind.  Making the trip now will also really help me to dive in head first with my new position and really grasp it as soon as possible.

At this very moment I am sitting in the Salt Lake City airport waiting for my first flight to Denver after having endured the hardest 24 hours I’ve had in a long time.

My wife Whitney has been extremely supportive of this position change and even this business trip because she knows that everything I’m doing is for the benefit of our family and is truly the best move for us at this time.  She has really helped me feel alright with leaving, even though I’ve been plagued with guilty feelings since I found out about trip, knowing that I was leaving my pregnant wife home alone for two full weeks.

Somehow I was able to go about my days until the trip without stressing too much, probably because I forced the thoughts to the back of my mind to deal with them when I had to.  But I knew the day would come when I would be leaving, and knew how hard it was going to be.

Whitney and I have known each other for about a year and a half now, and will have our one-year wedding anniversary on February 1^st, the day that I return from my trip.  During that time, the longest that we’ve ever been apart was for the one week when I was sent to Boston for FAST SME training.  After our marriage we’ve only spent one night apart, which was when my band played a show in Roosevelt, UT, and the band and I were put up in a hotel because our performance ended after midnight and it was about a three-hour drive home.

Because of this, we both knew that it was going to be really hard to say goodbye for such a long time.  This increased exponentially by knowing that Whitney is in her third trimester.

But to make the trifecta of goodbyes complete, my brother Easton is leaving on his two-year mission to Aguascalientes, Mexico, on Wednesday.  He has been preparing for his mission for a very long time and is such an incredible example to me.  Without a doubt I can say that he is very ready for his mission, and has prepared for it even more than I have for mine by studying the scriptures and the Preach My Gospel manual on a daily basis for weeks now and by attending the temple regularly with family and friends.

I was so disappointed when I found out that I would be missing his farewell talk in church the Sunday before he left because I would be on an airplane, and that I would not get to send him off.  But last Thursday Easton asked me to give him a Priesthood blessing to help him with his mission, which I was only too grateful to do.  It was such a humbling experiencing getting to place my hands on his head, jointly with my dad and brother-in-law, to give him a blessing of comfort, peace, and strength.

Also because I was leaving, Easton chose to come to our house last night to give me my own private goodbye.  It was very touching that he would do such a thing, and that he spent time with me, my wife, and my crazy dog before he left.

We talked about his mission and his preparation, and had a great chat.  We then said our goodbyes, and we all cried openly.  Believe it or not, with how hard it was for us to say goodbye, I think our dog Bronx took it the hardest.  He is very keen on emotions and sensed something was going on, and when Easton left our house Bronx bounded out with him and dashed down the stairs and down the sidewalk as if he expected to go with him.  After capturing him and saying another tearful goodbye to Easton, we went inside and Bronx sat at the door and cried.  This wasn’t the same whine as “I’m hungry” or “I’m bored, play with me,” it was a sadness in seeing Easton go.  It was funny and heart wrenching at the same time.

But even with how difficult it was to say goodbye, it was so wonderful to know that Easton was leaving to dedicate the next two years of his life to serving the Lord and being a literal representative of Jesus Christ.  I was—and am—so proud of him, and I just know that he is going to do miraculous things down in Mexico, and that the Lord is preparing people down there as we speak to learn of the Gospel through his words.

Even though I won’t get to be there for his send off, I will get to call him before he leaves to say goodbye once more, and have also packed paper, envelopes, and stamps so that I can send him some letters while I’m gone.

But now back to the most difficult goodbye of all:  saying goodbye to my sweet wife.  After Easton left our house, I can honestly say that it was difficult to keep it together, and a lot of tears were shed.  She is worried about me and my safety, I am worried about her and her safety, and we’re both sad at the fact that we will be so far away from each other for so long.  But I had the wonderful opportunity to give her a Priesthood blessing last night as well, which I believe really helped us both.

It is difficult for me to even fathom how it will be to sleep in a bed alone and be so far away from the person I love more than anyone else.  To me, two weeks feels like an eternity.  But I am so grateful that I will get to see her again soon and that, until then, I will be able to remain in contact with her on the phone and through text messages and even Apple Facetime if we want to.

I am also so grateful for the power of prayer and knowing that Heavenly Father will take care of the ones I love while I am gone.  It is truly a test of my faith to understand and believe in this principle, but I sincerely know that my prayers will be answered.

While saying all of these goodbyes has been very difficult, I know that I am where I need to be right now, because I am doing this for my family.  Because of that knowledge, I am going to get out to Virginia and work my very hardest to grasp the concepts and information as quickly and comprehensively as possible, so that I may come home and apply my knowledge to assist my career even further, and to know that this trip and this heartache was not in vain.

I also know that my faith and testimony will increase dramatically from being away from my sweet wife for so long, as it will cause me to depend on the Lord more than I have been recently, and to trust in His power.  And when I get home, I know that I will take Whitney in my arms and never want to let her go again, because I am certain that our love for each other is going to increase tenfold over the next fourteen days.

What on earth does Jeff actually do?!

I have been wanting to sit down for a while now and write about my job and what exactly I do for forty hours each week, mainly because I feel so bad for my wife and family whenever they get popped the question and have to fumble around to try to explain it.  Even I have a hard time trying to describe it to people when asked, and usually have a few different explanations based on the technical understanding of the person asking the question.  Some of the responses I'll often give are....

• "I work in the IT industry."
• "I work in maintaining data centers."
• "I work with 'The Cloud' and data storage."
• "I am a tech support engineer."
• "I support Network-Attached Storage arrays."

That's just a small sample of the different replies I give to people who want to know what I do for a living.  But in reality, my job is pretty complex to explain.  In fact, even my entire title is an acronym:  FAST VP SME, which stands for Fully Automated Storage Tiering for Virtual Pools Subject Matter Expert.

That's certainly a mouthful, so I'll try to start at the beginning.

I work at EMC Corporation in Draper, which is an IT company that is most widely known for its storage arrays and its acquisitions of VMware and RSA Security.  Not being able to afford multi-million dollar computer equipment, I'd never really heard of EMC in terms of their data storage systems, but knew who they were because of VMware and RSA, which I was exposed to quite a bit while studying at UVU.

If there was one word I could use to describe EMC, it would be "HUGE!"  Especially after coming from a small business of maybe 80 employees, I was incredibly shocked to be surrounded by several hundred employees just in Utah, as well as hundreds if not thousands more worldwide, all supporting a large variety of products.

I was hired on as a Technical Support Engineer for the Symmetrix department.  I don't usually like to refer to myself as being in "tech support" because of the call-center stigma that is associated with it, because even though I work with customers in resolving break/fix issues, I think the term "technical support" doesn't do my role very much justice.

But I'm getting ahead of myself.  I think I should first explain a little bit about what this Symmetrix thing is.  The Symmetrix storage array is the first product created by EMC, and is what is called a Network-Attached Storage (NAS) array.  These arrays look like giant refrigerators that line up beside each other like a football team on the scrimmage line, and are filled with hundreds or thousands of hard drives.  

Why on earth would someone need so many drives?  Well, just think about it.  If you're reading this post, then chances are you have a Facebook account, unless somehow I'm way more famous that I think I am...which is not very.  How many photos and videos would you say you've uploaded to your account?  Hundreds?  Thousands?  Ok, now ask yourself how many users exist on Facebook right now?  I sparked my own interested just now and Googled the answer, and it turns out that Facebook has about 1.19 BILLION active users as of October, 2013.  So multiply that number by the number of photos and videos you have on just your account and see what you get.  I'm not sure my calculator even goes that high.

Well, all those pictures have to be saved somewhere, and that's a LOT of storage space.  That's where storage arrays like the Symmetrix come into play.  These powerful machines can hold petabytes and petabytes of data, and make sure that it's ready and accessible every time someone needs to use it.  These arrays have loads of features to make sure that the data remains intact no matter what by having several backup power supplies, spare replacement hard drives that will kick into gear the moment one starts to fail, and even the ability to have a mirrored system set up hundreds of miles away just in case a major disaster occurred in the area like an earthquake or tornado and the primary data center went offline.

I was trained to support these arrays for all of our customers (which are pretty much all Fortune 500 companies) and make sure that there are no problems accessing their data at any time and at the speed that they want.

The Symmetrix has a really interesting system in place where it actually complains automatically to EMC whenever it's having any problems.  This "call home" feature allows the array to automatically dial home to an EMC server with any issues, which in turn automatically opens a support ticket for my team to investigate.  These "dial home errors" that dial home arrive in the form of a four-digit hexadecimal number with a two-digit modifer number which refers to a specific error.  Some examples of these errors are 24AF.78, 01B3.C0, 0471.02, and 033E.38.

This was probably one of the hardest parts of the job, learning how to decipher these codes to know what they are referring to.  One may refer to a failed drive that needs to be replaced, whereas one may refer to a backup power supply that won't hold a charge, and another could indicate that a cable was plugged into the wrong jack.  I look at the list of errors now and am still surprised when I know what they mean, when they looked completely Greek to me months before.

This is why I say that we are not the "traditional" type of technical support center, because in our case we will receive a report of an issue and have it corrected or a local representative onsite with a replacement part before the customer even knew there was a problem in the first place.

The way we do this is by remotely accessing a laptop built into one of the arrays, which is called the service processor.  The same way that I'll patch into my dad's computer to help him get rid of a virus or install a program, I can connect to an array in Sweden or Australia or anywhere else and remotely troubleshoot issues.

My primary role when I was hired was to investigate and resolve these dial home errors, which I performed until I was enrolled in a two-week course taught by a colleague from our Hopkinton, MA, office.  James Nigrelli was a Technical Support Engineer (TSE) like I was, but he had been flown out to Utah to teach me--along with a small group of people--about a new feature in our top-of-the-line Symmetrix VMAX arrays called FAST VP, or Fully Automated Storage Tiering for Virtual Pools.

This feature is surprisingly exactly what it sounds like, although it probably makes no sense to anyone reading this at the moment.  But in a nutshell, here's how it works.  There are essentially three types of drive technologies that make up a storage array.  The first type is called SATA, which is the hard disk that most of us are used to, with the spinning metal plate touched by a spindle used to read and write data, making it essentially look like a tiny vinyl player if you were able to see inside its chassis.  Next comes the Fibre Channel (FC) drive type, which is essentially a SATA drive but with a much faster, optical connection and a faster speed.  Third is the Enterprise Flash Drive (EFD) type, which is an Enterprise version of the Flash or Solid State technology, which is what you'd find in a USB thumb drive, your iPhone, or even some computers like the Macbook Air.

Obviously the faster, better drives are going to be more expensive than the slower ones, and customers want to make sure they're getting their money's worth out of them.  FAST VP is a completely automatic system built into the VMAX arrays that collect performance statistics on the data and then uses those statistics to make sure the data that is "hot" and being used all the time is being kept on the faster drives so they can be accessed quickly and that the "cold" data that isn't being used very much stays on the slower, less-expensive drives.

Did I lose you?  Well, then think of if this way.  Let's imagine you are a fashion extraordinaire and have a pretty extensive wardrobe, but just moved into a small apartment with only one closet.  With all of the clothes you have, you're going to need to keep them in three different locations: your closet, the garage, and at your parents' house.  Naturally you're going to want the clothes you wear all the time in the closet, the clothes you might wear every now and again in the garage, and the clothes you own but really should have been given to Goodwill a long time ago at your parents' house.  It's the same thing with FAST VP, but with data.

I really enjoyed learning about FAST VP and, after James returned home, I soon became the "go-to guy" for any FAST VP-related cases that were opened.  I had such an aptitude for it that, one year ago, my manager approached me and informed me that he wanted to send me out to the Hopkinton lab with another TSE named Richard Kimball (no relation to Harrison Ford) to study FAST VP "from the masters" in order to become a Subject Matter Expert.

The trip was incredible, but also difficult because it was one week before my wedding.  But I learned a ton, studying alongside James and his mentor Rob Tasker.  They taught me so much, and I was able to experience the busy life of those in Boston for a while, which actually made me pretty grateful that the Utah lab is a bit more mellow.  I also had the opportunity to meet the Symmetrix developers, including the programmer who invented FAST VP, who shockingly is actually a pretty young guy.

Upon returning from my trip, I was bestowed the title of FAST VP SME, or FAST SME for short.  Richard and I then became the first escalation point for Utah TSEs before having to escalate to the Hopkinton lab for help with FAST VP-related issues.  

A few months later, James announced that he had taken a job in the development team and would be leaving the support lab.  Shortly after that, Rob announced that he was being promoted to the L2 Support Team, which is the elite escalation team for all cases.  While he would still be a resource for troubleshooting FAST cases, I soon found myself to be the primary escalation point on a global scale, as I have a Monday through Friday shift and have more of a full exposure to the feature than Richard, who works on a rotating shift and will often spend up to a week at a time away from the lab.

Being one of two FAST SMEs on shift globally during the US business hours, I had a lot of responsibilities on my hands.  Not only was I expected to take all the FAST-related cases that appeared in the support queues and act as an escalation point to others, but I also participated in weekly and bi-weekly conference calls with the developers (referred to as Engineering) that I met in Hopkinton to discuss current and new issues that affected the feature, participating in a group called the FAST Task Force.

I have truly learned a lot while in this position.  Not only have I had to stretch my technical understanding to great lengths in order to understand the abstract concepts behind the product I support, but I have also had to hone my customer-facing skills as I have grown accustomed to sending dozens of emails each day and participating in several impromptu conference calls throughout the week.  I also became very adept at writing knowledgebase articles and other technical documents to help my colleagues in diagnosing various issues relating to FAST VP and its counterpart technology known as Virtual Provisioning.  (I'm not even going to attempt to explain this concept, as it's much more complex than even FAST VP!)

This job has been really wonderful, and yet very stressful at the same time.  More than occasionally would I go twelve hours without eating anything because I had to work through my lunch, and would come home with throbbing headaches from swiveling between my four workstations.  But on the whole, I really loved my job and felt like I lived up to expectations.

You may have noticed that I have been using the past tense when describing my job.  That is because I announced today to my team that I have taken on a new role as a TSE II in the RSA Security department, supporting the Security Analytics (also known as the NetWitness) platform, which is a tool for identifying and putting a stop to hacker infiltration attempts.

As I obtained my degree in IT Security, this has been pretty much what I would call my "dream job."  I always wanted to work in the IT Security field, keeping hackers at bay and fighting the virtual battle on the cutting-edge of technology.  I now hold a position in one of the leading IT Security companies worldwide.

This role is going to be much different than supporting the Symmetrix storage arrays, as I will be forgetting about hexadecimal error codes and proprietary software commands, and will instead be returning to my Linux roots, which I couldn't be more excited for.  I'm also being sent on a two-week business trip to Washington DC and Virginia in a few weeks for extensive onsite training to learn more about the product that I'll be supporting.

To say that I am excited would be an understatement.  This job opportunity also came at the perfect time, as Whitney and I will be having our first child at the end of March, and have had a lot to do in order to prepare for his arrival.  It really was a blessing that I discovered the offer when I did, so that I could take advantage of it and make this huge change in my life.

While I'm afraid of leaving the Symmetrix team, especially as I will be putting the burden of my role onto others' shoulders, I definitely feel like this is the right move for me at this time, and that I am doing what is in the best interest of my growing family.  But I am also so relieved and grateful that it includes starting a role in the job I've always dreamed of having.

Here's to the future!