The Burnout
Hello employers! I’m glad you made it to this blog. I hope to share an experience that most other developers go through during the job search. Most of the recruiters I’ve had the pleasure of meeting do not have a technical background so they can’t relate. If you do not have a technical background and are a recruiter, this is for you.
For the first time since I’ve picked up programming, I feel burned out. Why? Well looking for a job feels like a job. I wake up around the same time most people start their jobs, and I start to study. I’ve picked up on different technologies every month or so in hopes of making myself a unique frontend engineering candidate while also somehow trying to hold on to the technologies I already know. As I’m sure you know, most people don’t recall the things they learn 3 months ago while learning new material. How many times have you learned something in school only for that same information to be forgotten?
In the software engineering discipline, it’s almost expected that you practice coding everyday, especially as a rookie. You’ll find that when you learn one technology, you forget another. So what do you do? Well, you review. You review everything until it comes back to you and then you go back to your new material.
Right now, I’m currently learning NodeJS and although I love it, I relate it to Ruby on Rails because that’s the previous technology that I knew. The reason I decided to learn Node is because Rails is barely used anymore. As a software engineer you’re expected to keep up with new technologies.
The technologies you already know will also inevitably get an update and will give you a set of new material you’ll need to learn. As a software engineer, you’re expected to keep up with the new updates for the technologies you already know, even it perhaps you haven’t used it in quite some time.
Regardless of whether you are going for a frontend engineering role or backend, you’re expected to learn and fully understand data structures and algorithms. Personally, because I went to a bootcamp, I’m at a disadvantage to those who attended the traditional four year university. And many times people will ask “well, when is this material even used?” and it’s used everywhere but not in the same way a code assessment shows it to be. Code assessment seem to be much tougher than what’s actually expected in the office.
Being new to tech, I’ve learned that there’s so much material to learn. I pick my material based on what I believe is important. Currently, I’ve seen many jobs using ReactJS and NodeJS which is why I choose to practice them. I’m also interested in AWS so I learned a bit about that as well, coming across it through word of mouth. Which brings me to my next point. As a software engineer you’re expected to actively engage in new podcasts, shows, or news outlets that talk about new technologies. I find this to be a ridiculous expectation because outside of this thing that already takes up so much time, I’d like to participate in other hobbies. It’s almost like employers expect an individual who’s entire life revolves around tech but that’s not realistic. I’m a software engineer, photographer, videographer, adventurer, guitarist, brother, son, and uncle. I’m much more than a software engineer and refuse to lie and say that I’m always learning about tech 24/7.
What I will say is that I try my absolute hardest every week to find a company that I can impress and that I’m genuinely interested in. But questions like “How are you learning about new technologies” is always a head scratcher. I reply with “Well, I learn current technologies that I notice companies are either moving towards or actively using”. I don’t listens to podcasts, watch youtube videos, or watch shows on new things…because I haven’t yet become a master at what I’m currently learning; so those other technologies are not a priority to me. It’s almost feels like I’m being asked if I know different languages exist. Of course I know they exists, but what does that have to do with the job that I applied to that entails the stack I know?
So, why am I burned out? It’s because I wake up early to build out my current projects on React or Node, study algorithms on data structures which often takes time to solve, applying to jobs to make sure I fit the requirements, creating cover letters, interviewing back to back with companies, complete code assessments, completing my Flatiron school requirements, and add a pandemic into the mix and it gets a bit stressful.
I think it’s safe to say that most people feel this way but don’t often write about it. It’s an experience unique to developers or software engineers. To keep a positive head space, I’ll be taking a break and if you find that this blog is too close to home I suggest you do to.
Happy Coding.
