Dreaming in code

So after I had returned back to the main office in CT, crunch time was on. We had gotten all the information we could get from them and now the actual development work needed to be done. I was busy from the second I walked in the office until the second I left and it was amazing. Every day I was learning something new, figuring out clever ways to efficiently query the data warehouse, and trying to understand this complex world of deducibles and special billing to end-stage renal disease. Who would have thunk kidney disease gets billed differently?

Eventually, this project got pretty monotonous and repetitive. Luckily for me, a new project was brewing for me at Connecticare, in Farmington, on-site. I was on a team with my last projects’ manager, Tracy and a business analyst. We were tasked with creating an application that the insurance company would be using internally to audit claims. The requirements were very prescriptive. I had to use WCF. I never used WCF. I had to use Asp.Net Web Forms. I made 2, maybe 3 basic website with Asp.Net at the time. I had to use their enterprise level bit masking security scheme. What the hell is bit masking?!

During this first 2 to 3 weeks of the projects inception, I spent a whole lot of time taking courses on Pluralsight and reviewing sample programs that use their prescribed enterprise architecture. The architecture of the windows services was so overy complex. Death by architecture.

At the time I was experiencing serious symptoms of imposter syndrome and was dreading figuring this crazy architecture, but now I understand what the enterprise architect that was enforcing these standards, was actually trying to accomplish. Reusability, autonomy, and a standardized service inventory. I soon got the hang of it and was on my way to creating what was in essence, my own project that was going to be heavily used. Yes there was a PM and a BA who assisted in requirements and documentation, but the product itself, was mine. Under these supposition, I wanted to put my all into this application. I wanted to work harder on this than any other school or work project. This was my legacy at this company and I didn’t want that to be a half assed job.

To accomplish this, I was working 70 hour weeks. After about a month of that, I came to the realization that continuing to put in that many hours would damage both my physical and mental health. I started dreaming in code. It was terrifying at first but then the answers I was looking for would start coming to me, which of course was to be desired. Physically, I started gaining weight and just generally feeling lethargic and losing energy. I started cutting back my hours to around 40-45 a week and those issues started to dissipate.

My application was pretty well liked as far as I know and I was content with the job I had done. It wasn’t the prettiest, but it was exactly to spec on the approved mock ups. I then had to hand off my creation. My baby. What I had worked so hard to create. I spent about a week meeting with one of the Connecticare employees who would then be responsible for maintaining my application. To be honest, he seemed just as offput as I when reviewing the architecture that was mandated. But I did my best to cover everything about the application that I could.

When that project was over, I was moved to work on a project for Blue Cross Blue Shield of Vermont. This was a DB2 conversation project and I was intrigued because I had never used DB2. About 2 weeks into the project and I started dreading coming to work altogether. Not necessarily because of the work, but I was doing another project solo. I wanted to work on a team. To feel valued. So I started interviewing at different companies. I found one in particular that would cut my commute in half and about 50% more in salary. I figured, why not?

I leave you with this final note: Never stop interviewing. The market is constantly changing, new interviewing techniques come out, new technologies, etc. You need to stay current. You need to stay relevant. If you’re not getting harassed almost daily by recruiters on LinkedIn or phone calls, you aren’t putting enough effort into your career.

“There is no illness that is not exacerbated by stress.” ― Allan Lokos

Lessons Learned:

  • Pluralsight is an amazing resource for both technical and non-technical folks.
  • Sometimes you need to pull a lot of hours but be aware of how your body responds to that much stress. Long days like that aren’t sustainable.
  • Don’t be afraid to interview at other companies. This is to be expected if you are a valuable employee.

I shot a man in Reno just to watch him die (First business trip)

I started my first non-intern development job at SMC Partners in Hartford. The company is a systems & management consulting (SMC) for the health insurance industry. Keep in mind at this time, I was just fresh off my first internship and had absolutely no knowledge of the health insurance industry besides going to the doctor for my annual physical with a $20 copay.

I was commuting roughly 60-90 minutes depending on traffic. This didn’t bother me too much because at the time, I was beginning the work for my Bachelor’s degree at Central Connecticut State University, which is located in New Britain — about 15 minutes from the office. I’d be driving basically that far anyways, so it worked out.

The health insurance industry is incredibly complex. This is in part because of the differences in law between state insurance regulations and the other part being because of the various business areas that encompass the entirety of health insurance systems. Overwhelmed with the complexity of my upcoming work, my manager reassured me that, “If you can figure out the health insurance industry, you can figure out any company out there.” That gave me some piece of mind at the time and was some pretty decent advice.

My second week at this job and I was assigned to assist with the development from the ground up of an enterprise data warehouse for Hometown Health in Reno, Nevada. Some of the tasks that needed to be completed were designing the ETL process, designing the structure of the tables, and consolidate & parameterize approximately 550 reports. I was told we were to use SQL Server Reporting Services (SSRS) for the reports, which at the time was brand new to me.

I was informed the following week that I was necessary for us, my manager and I, to go to Reno and visit the client on site. This is amazing! I just started and they are going to pay me to travel! I was beyond excited for this. This was about a month away, so in the meantime, I performed analysis on the reports and cataloged them into an access database.

When I finished my Reno prep work, I assisted a fellow team member and data architect, Keith Evans. Keith is a humorous irish guy that was incredibly well versed in all things data. He taught me the foundations of data warehousing, OLAP databases, and ETL. He taught me that a star schema is preferred over a snowflake, he taught me about abnormal database normalization such as 5th normal form and higher, and taught me the power of SQL Server Integration Services (SSIS). I don’t think I enjoyed talking with any other co-worker as much as I did with him. I will be forever grateful for everything I learned from him because what I learned from him was incredibly unique skills to have with someone with my level of experience. And the most important thing I learned from him was that M&M’s from Ireland taste better than the American variations!

The time had come for my flight to Reno. We were only staying for the week but some clean mountain air would do me good. When we land, I discover the airline lost my luggage. So I had no clothes, no ties, no business wear, and was informed that the client perfred consultants to wear business formal. My nerves are at an all time high. Luckily, after getting the rental car, we drove to Marshall’s and bought a few outfits until my luggage was found.

The next morning we go to the client’s office after a restless night of sleep. This was my first ever real client meeting and had no clue what to expect. My manager begins discussions with the client and asks me to take meeting minutes. I never liked taking notes. Not in school. Not in work. But as a subordinate, I had to comply no matter how poor my notes were. I was so attentive to the content of the conversation because I was afraid to miss anything and disappoint my manager. It was exhausting hanging on every word everyone said. Is this what being a developer is like? I thought I’d be coding most of the time but here I am, taking notes for hours on end.

My luggage was found and delivered back to my hotel room at the El Dorado in downtown Reno. Now that I had my things, I was able to relax a little more and started exploring the casino.

Most of the week I spent at the client’s office, fighting off nose bleeds from that clean Tahoe mountain air, taking notes, listening, and meeting all the key stakeholders. Even though I did less than an hour of coding my entire trip, I learned the most about what it means to be a consultant. I left Reno, re-energized, reinvererated, and ready to learn everything I could in both the business and technological spaces.

If you think adventure is dangerous, try routine; it’s lethal.

–Paulo Coelho

Lessons learned:

  • Commuting more than 30 minutes one way is not sustainable for a long time.
  • Complex industries make development work more interesting.
  • Never check luggage on business trips.
  • When at higher altitudes, drink more water.