Two years into my first software engineering job
Tags: career
Published: 2019-01-19 23:36:56

---
title: Two years into my first software engineering job
published: true
description: A scrum retrospective of my first two years as a software engineer after finishing my coding bootcamp. What a ride!
tags: career
---

![Year 2 - Photo by Sonny Ravesteijn on Unsplash](https://thepracticaldev.s3.amazonaws.com/i/yor80k4o0mk2lbccxwtj.jpg)
_Photo by [Sonny Ravesteijn on Unsplash](https://unsplash.com/photos/xyxjKdpUg4I?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_

In the blink of an eye, I'm now at my second anniversary at my first engineering job. I thought it would be a good opportunity to sit down and gather my thoughts (since I never did the first anniversary write-up).

### High-level background info:

I'm 37 years old, work in Silicon Valley, have a BA in English, and had over 12 years of experience in customer-facing roles before going to Hackbright Academy (an all women's coding bootcamp in San Francisco; [blog post on the experience](https://medium.com/@wordswithchung/what-i-learned-through-my-three-month-coding-bootcamp-ab5124a91d96)) and then becoming a software engineer.

In the spirit of scrum retrospectives, let's list the things that went well, didn't go well, and could be improved over the past two years. Starting from negatives to positives.

### Not well:

* I continue to have bouts of impostor syndrome. Every now and then I'll be working on a big, highly-visible feature and think, "Holy crap, why would they give me this project? Don't they know I've only been coding for less than two years altogether!?!!!!!?!? I STILL DON'T KNOW HOW TO TRAVERSE A GRAPH ON THE WHITEBOARD." And when that happens, I let the thought come and go and remind myself, "Chung, this isn't the first highly-visible feature that you've worked on. And the last one you worked on, you delivered it on-time and to-spec. You'll most likely do the same on this project, too."
* I still make bugs. (Read: HOLY CRAP, I'M HUMAN AFTER ALL!) I refer to it as "job security" to lighten the mood but, they happen and they are oh so humbling.... And I'm learning to accept this truth (while still trying to minimize the bugs).

### Well:

* I've learned so friggin' much. When I first started at my job, I was on the backend team and had to ramp up on Java. (We learned Python at Hackbright.) Six months in, I ended my backend rotation and went over to the frontend team and had to learn Angular and fully embraced my love-hate relationship with Javascript. I have: updated the DB schema, checked a ton of code that now lives in production (and a lot even in the main dashboard of our product), optimized code for performance, created API endpoints, implemented Apollo client in our codebase to use GraphQL. The list goes on and on. This is definitely the thing I love about software engineering and look forward to doing more.
* My codebase knowledge + my hyper-organized tendencies ([evidence]( https://dev.to/wordswithchung/managing-your-personal-sprints-wtrello-3adg)) = ridiculous productivity. I think back on when I first started and I struggled _so much_ with everything. (_Ugh CSS_. _Ugh installing Node_.) Now I'm able to restructure how we parse a ton of entities and generate a brand new page / component within a week's time. All the while, helping to review code, answering questions*, and moving projects along. Hooray, productivity!
  * * Segue about answering questions: Remember how I mentioned that I worked in customer-facing roles for 12+ years? Turns out that answering technical questions doesn't really require a lot of specific technical knowledge, but rather 1. a keen eye (thank you, BA in English) and 2. a boatload of patience. When folks come over to ask me questions, I patiently listen (even though I have _no idea_ what the actual answer is) and half of the time, by the end of telling me, they'll have figured it out. Or as they walk through it, I'll spot a typo or an errant space and boom! problem solved.
* I've been rewarded for my hard work, from a raise, promotion, and [winning the "Values in Actions" award](https://twitter.com/vinayspai/status/1063159437421043713) at the company-level. It's really nice to be recognized and appreciated for my contributions. 
* Before making the decision to quit my comfortable job, going to a bootcamp, and venturing into a career I didn't know much about (at age 35!), I was legitimately worried that I wouldn't like it. I'm happy to report that after two years: I love it! The computer-facing work suits my introverted heart nicely (read: not client-facing, not a ton of meetings). And the detailed, technical work itself is challenging and highly addictive for someone like me. 

![Comic about programmer never getting sleep because bugs](https://thepracticaldev.s3.amazonaws.com/i/4efsh4nk5f7fwwpdz749.jpg)

### Improvements:

* I feel my learning plateauing lately, which is natural, but I shouldn't let that inertia build. There's still so much I want to learn, and I need to prioritize that.
* I definitely haven't hand-lettered as much punny code as I could:

![recursion written in cursive](https://thepracticaldev.s3.amazonaws.com/i/fbnz86nw8358v452v5tw.jpg)
_See on [Twitter](https://twitter.com/wordswithchung/status/811320080185233408)_

![let this promise console.log(you)](https://thepracticaldev.s3.amazonaws.com/i/jtwx9d0u804f8obmca9g.png)
_See on [Instagram](https://www.instagram.com/p/Bo45P0BgIf3/)_

Yep, that about sums it up. Two years gone in a flash. And if this diagram that I drew of [Ken Mazaika's post](https://dev.to/kenmazaika/heres-what-you-can-learn-in-10-minutes-that-will-be-useful-for-the-rest-of-your-programming-career) still holds true, I'm officially an "experienced dev". Woohoo!

![experienced vs. inexperienced devs](https://thepracticaldev.s3.amazonaws.com/i/vrigjzmb7z2mvcbr8epn.jpg)
_See on [Twitter](https://twitter.com/wordswithchung/status/811320080185233408)_