One of my roommates in college was a Comp Sci major. Since she spent all hours of the night working on labs, I assumed she had chosen the wrong major. I had no idea what she was doing.
Fast forward a few years later and I’m an analyst on the tech team of a cleantech company. I got to learn SQL on the job, and while it’s not exactly coding, I got my first taste into what it’s like to make a computer do what you say. I’ve always been curious about what is going on behind the scenes or underneath the hood, so when our tech team built new landing pages for marketing, sales agent management for sales, or our new products, I was interested in how they were doing this. At the same time, I was managing bugs that our member support team came across. I grew increasingly frustrated that I could help to define both the bugs and its scope, but I had to stop there and pass it off for the developers to fix.
I got my start by taking a HTML/ CSS class with a local non-profit. I knew I was on the right path. I followed up by taking classes on web accessibility, the command line, and intermediate HTML/ CSS. I was equal parts confused and excited. To me, not completely understanding something is exciting because it means I’m challenging myself to learn something outside my comfort zone.
My desire to learn how to code is fueled by my desire to break into a field which fosters an ever learning, flexible, and meaningful career.
In yoga it is said to always be a student, no matter how much experience you have. I like to take this concept in my every day life. I challenge myself to read books across vast topics, attend yoga workshops, learn new skills (stitching being the most recent!) so I can continue to make connections and recognize patterns about the world around me. Like I mentioned earlier, I take not knowing something as an opportunity for growth, and it seems as though there is no ceiling with programming.
As I’m getting older I realize I won’t always want to live in a city, where most startups and innovative companies tend to incubate. Becoming a developer will help to find remote work. I love the flexibility of not being bound to an office in order to get work done. I think employees should be trusted to get their work done, no matter where they are. Another aspect of flexility is the vast amount of roles a developer can fill. There are SO many different types of roles and industries I can break into. I can teach, be a part of a solid engineering team at an emerging startup, or freelance— it’s tough for me to see where I’ll land after completing my bootcamp because there are so many possibilities!
What was astounding to me when I first started to research my career transition was that every developer seemed beamingly proud of their job. As I began to learn how to code, I started to realize why. Software developers of all kinds are building our future. Developers can bring an idea to life. Personally, it’s powerful that I will be able to bring my idea of a yoga class plan generator or an app to teach Tarot to beginners to the world!
What also adds to a meaningful career is the community. I’ve received so much support from both strangers and new friends, whether it was through twitter and using the #100DaysofCode hashtag, or meeting people in real life at local tech MeetUps. I know I’m not in this alone.
I find my reasons to learn to code are evolving. I didn’t pursue this career shift because I thought “Hmm, I could certainly use a larger professional network,” or “Let me pick a field where I’ll continuously feel like a novice”, — these are byproducts. The reason why you start on a trek is never the reason why you finish it. I’m looking forward to watch my motivation to keep learning unravel as I go deeper and deeper into a programming career.