I remember when I was a child, time seemed to move so slowly. The school year creeped by. From the start of the school year until Christmas took forever. And then heading back in New Year, the spring break seemed so far away. Winter dragged on for ages.

As I got older, obviously my perspective changed some. But time definitely did not fly by. In my twenties, the seasons still seemed to drag on. I’m not quite sure when all that changed, but it definitely has. Weeks and months fly by now. Even the hot, sticky summers don’t seem to last as long as they used to and I know that the weather will soon turn cool as the leaves start to change color.

Just over one year ago I was let go from my job. My position was eliminated, and I was given my notice. I was in shock. Though I hated my job, I had felt very secure. Some months earlier (spurred on my a lackluster annual raise and lack of advancement potential) I had decided that I hated it enough to make some real changes in my life. I started to pursue options for a new career. But given the luxury of a stable (or so I thought) job, I was in no hurry and did not feel any pressure. Then I was let go. The timing was not great, as I was nowhere near prepared for a new career. I gamely tried to find an entry level developer role, but my skills were not sufficient and entry level roles are like unicorns.

So, I had to make the decision to continue pursuing a new vocation whilst looking for a new job that was the same as my old role. It was a little depressing, but I told myself it wasn’t forever. Unfortunately, it took a bit longer to get a new job than I thought it would. It knocked my confidence. And when I did finally get an offer, I was conflicted by my feelings. I didn’t really feel happy about it, but I was relieved not to be unemployed. The disappointment of the role was tempered by the fact that it was with a very large tech company. At least I would be in the industry, if in a non-technical role. Maybe I could even transition within the company once I was qualified.

I started my new role about the same time I started the full stack web development boot camp. I didn’t really think I wanted to be a web developer, but I did want the structure of a boot camp and I wanted to have the full stack experience so I understood both front and back end. While I do not regret that decision, it has not turned out quite as I had planned. Well before the boot camp was over, I knew I had no desire to work in web development. I also realized I wasn’t interested in front end development. I started to question if software development was really what I wanted after all. So I started to dabble. Knowing how to code can be beneficial to any number or roles, so maybe I should start looking at some other options. I did some research into QA and testing. I had a background in QA, so it seemed like it might be a good fit. However, I just didn’t feel passionate about it. Every time I would take some training on testing software, I just felt no enthusiasm. And I quickly realized there was so much to learn before I would be employable. With no drive to make me learn more, I drifted away from the training. Now what?

I started to look at other options for roles in tech. However, most were things that I had no interest in or didn’t feel I had an aptitude for. I had no interest in sales. Having worked in marketing, I knew that was not anything that would make me happy. Recruiting? Hard no. Product management? Meh. I had done project management for years and knew that type of work was not something that would make me fulfilled. Too much time sitting in meetings with people trying to make everyone happy.

Something that did sound interesting was cyber security. I had been intrigued by that in the past, but figured it was something I did not have the type of skills or background for – it was out of my league. I remember over a year ago when I was on a virtual job fair, there was a woman in a company’s booth that had mentioned she has a certification in cyber security. The recruiter nearly bit her hand off trying to get her to give him her details. He said they really needed people, especially women in that field. I remember thinking “lucky her!” But that felt like something that was completely foreign and unattainable. I wasn’t a “hacker” type, so that ruled that out. However, I had the chance to learn more about different types of roles in security. And it turns out, there’s a lot more to it than hackers. There’s roles that need people like me who enjoy puzzles, and sifting through lots of data to find answers. There’s roles that need people who are excited about the prospect of setting up rules and making sure companies are adhering to them. There’s loads of roles that require technical know-how but not a desire to crack a system and steal data. So there might actually be a role for me.

A year ago, I was lost. I had no idea how things were going to pan out or how I was going to make a transition into a new vocation. And I felt a bit of panic thinking I needed to have all the answers and make it work within a couple of months. I didn’t. I still don’t. But I know all I need is time. And that time is going to fly by just as the past year did. I can’t wait to see where I go from here.

Go Deep, Not Wide

Self taught developers have a distinct disadvantage when it comes to learning: lack of structure. Those who have taken a traditional route and gone to college to earn a Computer Science degree have a strict curriculum that they follow. It’s a clear path.

When I started into the world of tech, I had no idea what I didn’t know. I mean, I knew I didn’t know anything. But the specifics of what I needed to learn were not clear. And they won’t be for anyone. There’s so many paths, so many languages, so many niches, that it’s overwhelming. Trying to figure out what you want to study is extremely difficult, since you haven’t been exposed to a lot of these areas. I found when I first started, I thought I knew what I wanted to do but as I discovered more things it was like cracks in a windowpane, appearing and leading off in a million different directions. I quickly became overwhelmed. One day I’d think: “I’m going to specialize in SQL” then the next “I’m going to learn Python” and so on. I would read something that would send me down a rabbit hole and next thing I knew it was 4 hours later and I had bookmarked dozens of websites to return to and investigate.

I read a post on Twitter the other day that really resonated with me: don’t collect materials. Don’t bookmark a million things thinking you’re going to come back to it. Don’t think “I’ll read this later” but click on the hyperlinks to new sources to check out, then repeat. It’s a dark hole. And chances are, you won’t come back to those links anytime soon.

Some of the investigative coursework and reading I did earlier on was helpful. I purposely stepped back at one point and did some entry-level computing courses on LinkedIn learning. I did a course on object-oriented programming which was not language-specific but introduced theory. These gave me a good overview of the basics (What is the internet, how does it work?) and I would recommend anyone do that first.

But then once you get an idea of what path you want to take, map it out and stick to it. Do not get distracted by the pretty, shiny things out there that you’ll hear about on Twitter and LinkedIn or in forums. Stick to your path, learn it well. Those other things will be out there once you complete your entry level work, but trying to do everything at once will leave you exhausted and defeated. In fact, I would go as far to say that once you have decided on a path, do not even click on those Tweets that are threads of “resources for new developers” or “learning paths” – everyone has their own opinion and you can’t keep jumping from path to path if you’re going to get anywhere.

This does bring up one sticking point: how do you know which path to choose to learn? My best advice is to pay attention to what works for you when you are doing your investigative learning. Are you finding videos to be most helpful? Maybe Udemy or Coursera is best for you. Or are you more of a reader? Odin Project is awesome. Perhaps a more hands on approach works best for you. Try Scrimba.

The point is, find out your learning style and THEN find the training materials to help. Then stick with it. After the initial rush of energy to try something new, you will feel as though it’s a slog. Just stick with it. Push through and remain committed. Do not jump tracks. Deepen and refine the skills on that path before you consider moving on to something else. You do NOT want to be “jack of all trades, master of none” when it comes to tech. Companies want to hire you because you are competent in a skill they need. Even if they hire you to learn a different language on the job, the fact that you have deep knowledge with one language will make it much easier to learn the next and shows them that you have tenacity and focus.

Bottom line: choose a path, then go deep, not wide.

I Am A Software Developer

A few days ago, the instructor of our bootcamp told us to announce to the world we were software developers specializing in front end web development. As it turns out, that was easy for some of us but very hard for others. There’s been a few of us that took our time and tip-toed into that announcement. But I’m starting to trust the process a bit more and am gaining confidence with the public part.

Quite frankly, I don’t think anyone else really cares if I say that or not. Even if there’s someone who mocks us as code newbies who are a bit above their station, does it matter? The vast majority of people who see me or anyone else on social media say something like that will just keep reading and not really take any notice.

The instructor has repeatedly said that thought he boot camp is free, the “cost” will be that we are expected to help pull people through into tech. He says once we’ve made it, we should help 3 more people get into tech. This is something I feel very passionate about! My focus will be women like me. I would love to help more “mature” women realize their potential. I know there are so many like me who have been told “no” enough times in their lives that they believe it, and I want to help fix that. I’ve started to get more active on social media, and to comment more on some of the gatekeeping I have seen and been subjected to. I really want to call that out and be part of the change to make sure it is not normalized.

Right now my primary focus is on me making this transition to tech, but I can definitely see where I plan to make a difference in the future.

Old Dog, New Tricks

Today during my class office hours, there were several people asking about ageism in tech. Apparently there’s a lot of us who are over 40 in this cohort.

Honestly, I’m less concerned about the ageism in tech as I am about how well I can learn and retain things at my age. When I was 20-something, I could stay up all night partying with friends and head out to work with 2 hours sleep to do a full day’s work. I rebounded quicker from things and had so much more energy. I seemed to grasp new things more quickly. As a more “mature” student, I have the benefit of real-world experience. I can draw on that to make connections to things and to realize what things are not really important. A younger student will ask a million “what if” questions in a class whilst someone like me understands you won’t be prepared for every situation before it happens. Don’t stress about that kind of stuff.

I do wish I had come to learning to code earlier in my life, but things happen the way they are supposed to, so I don’t overthink that point. I have far more tenacity about things I want now than I did when I was younger. As I make choices, I understand sacrifices and commitment to make them happen. My younger self was often pulled off course because I either couldn’t make up my mind about things or I was easily led astray. I know this is my path and I am so pleased that I’m where I am right now.