5 Things I Wish I Knew Before Quitting My Job to Get a CS Degree
By Kari Cheslock
March 28, 2022
10 min read
Subscribe

to this blog to receive future updates!

A person typing at a computer
Background

As I'm writing this post, it's been just over a year since I quit my job to go back to school full time. When the pandemic was in full force back in 2020 and we were all stuck at home, I took the time to re-evaluate my life. I hated my job. I was stuck there, burned out and at the cliched dead end. And thanks to the pandemic I was also stuck at home with not much to do other than dread going back to work the next day.

Colored liquids in glass flasks

I was working as a chemist at a federal government lab, which may sound glamorous at first, but I'm here to tell you - government work is pretty much the same across the board. The pay is decent and the benefits are good, but there is little room for advancement and a lot of room for burnout.

The rumors are also true - it is impossible to get fired from government work. While this may seem like it could work in your favor, what it actually leads to is getting stuck working with the proverbial 'bad eggs'. A lot of them. And they are impossible to fire. I don't think I really need to describe to you the type of toxic work environment that this leads to. In fact, my job was toxic in more ways than one. I was handling toxic chemicals in the literal sense and dealing with toxic people in the figurative sense. Needless to say, I had many reasons to want to move on to something new. I didn't want a career that caused me to feel so much negativity and cynicism. I wanted a career that brought a sense of pride and accomplishment.

My point of all of this is that I took this opportunity, this re-evaluation of my career, to decide that I could make a change. The Great Resignation was really only a rumor at this point in time, but reading about that notion planted a little seed of thought. Maybe I could pursue a new career? It would be tough but worth it to regain a sense of having value in my career.

And so, after a lot of online research, I landed on computer science as a new career path and began looking around for a degree program. I chose an accelerated online program on an asynchronous platform that charged a reasonably affordable tuition. The courses were 8 weeks long, they took a generous number of transfer credits, and I had enough cash in savings to pay for the entire degree program without having to go into debt. Perfect.

A computer on a desk with a stack of books
Thought Process 🤔

I had a lot of reasons for choosing computer science.

  1. I had a math minor from my first go-round as an undergrad, so I figured that would help out in terms of transfer credits, etc., and give me a head start on finishing another degree quickly (it did).
  2. I had always wanted to learn to code even though I had never written a single line of code in my life (more on that later).
  3. I have been a massive consumer of tech products my entire life, so I thought it would be nice to know how they all work under the hood.
  4. I thought at the time that the industry best capable of surviving the pandemic was going to be the tech industry. This may sound a little paranoid now in 2022, but in 2020, before the vaccine was available and with large swaths of the population refusing to comply with mandates, it was impossible to know how the pandemic was going to play out. It seemed that the tech industry was more capable of keeping its employees safely working at home for an indefinite amount of time, and so that made a computer science degree seem a practical choice.
  5. And last, but not least, I tried some coding tutorials online and I thought it was fun. A simple reason but probably the best one. It seemed like I was going to enjoy doing it.

But this isn't a post about my reasons for choosing computer science. This is a post about things I wish I had known back when I was considering quitting my career of around 17 years and swan-diving (or maybe belly-flopping?) into a completely new career. Starting from scratch. Going back to the old drawing board.

Reflection

I can honestly say at this point that I have absolutely zero regrets. And that is a great feeling. But there are some things I wish I had known so that I could have done things a little better. And by that I mean, there are some things I wish I had known and wish I had done to put myself in a little better position to apply for jobs. Since I'm in the phase now of finishing up my last course (yay!) and starting to look for jobs, I'm realizing now that I'm a little behind the 8-ball as far as having a strong enough resume to be competitive for jobs. I'm in the process of making up for it, but I could have saved myself a little time if I had known these things.

Advice
  1. You really need to go above and beyond a basic computer science curriculum to have the skills needed for a job.
  2. You cannot and should not assume that the degree program you choose will provide you with all of the skills you need to be competitive in the job market. As someone who had never written any code before, I should have started out stronger, trying to learn as much as I could as quickly as I could instead of relying on the degree program to teach me everything I needed to know. Here are some things you should do right out of the gate when you start a computer science degree program.

    • Start teaching yourself as many coding languages as possible using as many online tutorials as you can get your hands on. There are a ton of resources out there to learn coding so try not to get overwhelmed. Just settle on one that offers a good variety of languages and start coding away. You will likely start to gravitate toward a certain language or languages over time and this will help you start to figure out what you like. If you really want a recommendation for a starting point, go with W3 schools.
    • Read through some “Getting Started” articles and blog posts. Again, there will be a ton of information out there, but look for some good advice that speaks to you and follow it. Also look for YouTube videos that are titled something like “XXX Language for Absolute Beginners” and watch someone coding live. This is a great replacement for live classroom instruction. Another recommendation here - the freeCodeCamp YouTube channel. They have a little of everything.
  3. Learn Git and GitHub as soon as possible and start posting projects to GitHub.
  4. This may seem completely overwhelming at first, but even the least little coding project that you can post to GitHub will be worthwhile. The reason for this is that a GitHub portfolio will be extremely valuable for your resume. Also, your GitHub profile will have a stat that looks like this:

    GitHub contributions grid

    This graphic shows how much you post to GitHub. As you can see from mine, I really only started seriously posting to GitHub in the past couple of months. The other posts over the previous year represent school assignments with a requirement to post to GitHub. I should have been doing much more than that. The idea here is that the more you post to GitHub, the more coding you're doing, which looks good to potential employers.

  5. Have a good social media presence, but in a professional and productive way that looks good on a resume.
  6. This may not be a difficult thing for many of you, but for me this is a huge undertaking. In fact, this blog post is my first real foray into improving my social media presence. You see, my former job required me to hold a security clearance with the government, and my husband currently holds a really high level security clearance with the government. While this might sound like a strange excuse, it is a little difficult to be involved with social media and hold a security clearance. Let's just say, it causes complications. But now, I'm realizing that I'm once again behind the 8-ball and need to improve things.

    Here are some things I'm going to be working on, and some things I can recommend based on my own research in order to improve social media presence.

    • Blog posts of a technical nature, or a listing of “Tips and Tricks”.
    • Tutorials explaining something technical and showing the code that goes along with it.
    • Dedicated profiles on the various social media outlets that only contain posts, connections, etc. that are relevant to your career.
  7. You're going to need a portfolio of completed projects in order to apply for a job.
  8. While building your own portfolio may seem like an unreachable goal when you're a beginner, you need to think about your education as the means to achieve a portfolio in the end. In other words, keep that in mind as your end goal and start working towards it from the very beginning. Look for tutorials that offer completed projects at the end. These are all things you can push to GitHub to show that you're coding regularly.

    And your portfolio should be something you coded from scratch and not something built with Wix or Wordpress or any of the other pre-canned website builders. You need to learn HTML, CSS, and JavaScript along with frameworks such as React or Angular or whatever one you find you like to actually code your own website and showcase your work. It's a big project but start coding early and often and you will get there.

  9. Practice, practice, practice!
  10. Ok, this is a little cliched, but I can tell you from a great deal of personal experience at this point that coding is very difficult to learn and it only gets easier if you do it. One of my best recommendations for learning is to follow along with a tutorial, make sure the code works at the end, and then delete it and try to recreate it on your own without the tutorial. This process will also give you debugging experience since your code probably won't work when you recreate it. And if you'll forgive another cliche - learning from your mistakes is the best way to learn.

So that's it. These are the things I wish I knew about a year and a half ago when I first started pursuing my new career. And while I mentioned several times that I feel behind right now and have a good bit of catching up to do, I'm not going to give up. This post will be the first of several discussing my goals and my journey towards a new career. I plan on having some posts discussing personal tips and tricks, like this one, and some more technical posts where I will showcase some things that I have learned and try to convey them as a series of tutorials.

Please comment below 👇 or send me a message 📨 if you liked what I had to say. You can also connect with me on LinkedIn .

Also, don't forget to Subscribe to this blog to receive future updates!

Happy Coding!

Kari


Sign in with Google to add a comment

Comments