The Journey to Fullstack, Part 1: The Beginning
October 12, 2016
From as young as I can remember, I wanted to be a doctor. I loved science and problem-solving and wanted to use the two to one day save the world. Partway through college, after a long period of insightful conversations and self-reflection, I came to the conclusion that medicine wasn’t what I wanted to do with my life, it wasn't going to be something I would find personally fulfilling, and it wasn't where I thought I could make the most impact.
I started doing basic statistical and graphical programming to see how my research results turned out, and then make pretty graphs of said results. (Because if nothing else, at least I had pretty graphs.) When the time came to figure out what I wanted to do after graduation, I figured I like statistics and R enough that I decided to become a data analytics consultant.
Fast forward a year, during which I learned more R, some SQL, and some SAS. I wrote some of my own code, and quality checked other people’s codes. I also started to learn some Python on my own, because everyone said you could do cool things with Python. I started realizing more and more how much I enjoyed coding, but was always dissatisfied with the little amount that I was able to do on the job.
So I started branching off on my own. I used Coursera to go extend my knowledge of R and Python during nights and weekends. I managed to get to a point where my company was willing to send me to a local Python conference, and immediately came out of it with the mindset of “I want to build EVERYTHING!” Except I didn’t know really know what I could build with the relatively rudimentary skills I had taught myself. (I was slightly disappointed, though not very surprised, when I found out that you needed more than that to build an R2D2 robot that would tell you the weather when you asked.)
Free Code Camp
While searching for project ideas or some kind of structure to help me go more in-depth, I came across Free Code Camp. For those who don’t know, Free Code Camp is an open source community with the goal of helping people learn how to code, and then allowing those people to work on real, nonprofit projects. I’m a huge fan of philanthropy and bettering our world and being a part of friendly communities, and I signed up for an account the same day I discovered it.
Why I Decided to Apply to Bootcamps
I was no stranger to the idea of bootcamps; I had read and heard enough about them to know they were a feasible option. I was skeptical of them at first. The data analyst in me knew that the 99% job placement rates had to be skewed somehow. I also knew I was capable, intelligent, and motivated enough that I could become a professional developer on my own, at absolutely no cost to me other than time. I knew I could cobble together my own online curriculum, given a lot of research and some time. I knew I could find my own niche community and my own mentors, given a lot of meetups and attending events and meeting with various people (and some time). Instructors who could devote their time to me would be a lot harder to come by, but I knew could make it work mostly on my own.
But, going to work from 7am to 6pm, eating a quick dinner, and then coding from 7pm to 2am every day was exhausting. I knew that programming and developing web apps and software was exactly what I wanted to do with my life, and I didn’t want the distraction of “real life” getting in the way.
I wanted the structure and that extra push to get things done that came with the programs. Free Code Camp helps in that it gives a more definitive path to follow than the wild goose chase that the internet can oftentimes lead you on, but I was still trying to cobble together internet resources to fill in sometimes rather large gaps. (For the record, I’ve been in contact with Quincy about some of these and they’re really trying to make it as comprehensive and thorough as possible.) I also had gotten to the point where I knew and was very comfortable with the basics, but I wasn’t quite to the point of being able to understand and attack a lot of the more advanced concepts. I was in a weird in-between in which I was having difficulty finding resources that catered to my level to learn from.
I also wanted a community of people whom I could seek help and mentorship from, as well as people who were learning alongside me. The Free Code Camp, CodeNewbie, and Women Who Code communities filled this void to some extent, but the people who knew what they were doing had commitments outside of me and my learning (shocker, right?), and there never seemed to be someone consistently in the exact same place at the exact same time struggling with the exact same things as I was. Both of these together often made learning on my own hard and lonely.
In the end, I wanted more structure, intensity, and community than I knew I’d be able to find or create on my own in such a short period of time. I wanted to stop worrying about whether learning Angular or React was better. I wanted to not spend hours and hours attempting to decode vague error messages from newly installed software and packages. I wanted to learn how to build scalable apps and adhere to best practices. I wanted to focus on actually learning how to program and solving problems through code, instead of spending a lot of my time trying to figure out what and how and with whom to learn and do.
And so I began looking into coding bootcamps. I sought out anyone and everyone I could find who had graduated from a bootcamp or who was working in the tech industry to get their perspectives on them. After months of internal debate, multiple pro and con lists, and some messages in the Women Who Code Austin’s Slack channel about various scholarships available, I decided to apply with the mindset of, “Why not?”
I knew it wasn’t going to be easy. I knew I would still have to put in long hours, and hard work, and networking, and frequently feel completely incompetent. I knew it wasn’t the magic pill in becoming good at programming or getting a job, and that I would have to put in even more hours and work and dealing with rejection to accomplish that. And yet, I was excited to struggle along with 15 other people, to learn more than I maybe ever have in my life in such a small period of time, and to dive head-first into the crazy world of programming.
Read the other blog posts in this series: