December 4, 2016
It’s been a slightly crazy week. I missed two days of class to attend Node.js Interactive North America, which was enormously fun and educational but also meant that I had two days of class to catch up on, in addition to staying on top of what we were learning every day.
I’ve spent most of this weekend doing some preliminary review for our upcoming Junior Phase checkpoint. (Basically, our “final” exam. It determines whether or not we get to move on to Senior Phase. You know, just a wee thing.) This has reinforced to me two things:
We’ve learned A LOT – there’s a lot to review!
Things that would have (and did) caused me headaches in week 1 are pretty easy now. I can definitely tell that my problem-solving ability, especially in the context of programming, has increased drastically; problems that I wouldn’t have been able to solve without significant help in week 1 only took a little bit of pseudocoding on a piece of paper before I was able to quickly implement a solution.
On the flip side, this week and this experience in general has proven to me that the more that I learn, the more I feel like I don’t know, in the absolute best way possible – there really never is a lack of things to learn and investigate and tinker around with. Though I’m starting to realize just how much I’ve learned and grown in the past five weeks, entire worlds that I had no idea existed prior have opened up to me this week.
I’m honestly a little surprised by how much I’m enjoying React. I don’t know if I should have been that surprised, considering I’ve been looking forward to learning it ever since sort-of-but-not-really learning it at the Austin Diversity Hackathon, and I’ve had an inexplicable propensity towards functional programming. I’ve been having a lot of fun with it, and I can’t wait to build a personal project or two over the break with it!
“So, what do you want to be when you grow up?”
The rapidly approaching end to Junior Phase means that we’re now gearing up for Senior Phase. I’m really looking forward to applying what we’ve learned to build out actual applications. But, it also means that post-Fullstack is a very real thing that we now should start thinking about, whether it be us joining the workforce or joining Fullstack as a fellow.
I really like the idea of being a fellow; mentoring and teaching has always been one of my favorite things, and I think it would be an incredible opportunity to continue my learning in an environment that I love. I’m planning on talking to both of my fellows to find out what their experiences have been like, and then I’ll weigh my options after that and decide if I want to apply.
If I decide not to apply or don’t get accepted as a fellow (both of which are very real possibilities!), that means job hunting, everyone’s absolute favorite activity ever, will definitely be happening. We just received a huge amount of information about what’s to come: from prepping our online presence and resumes and cover letters, to practicing whiteboarding with our cohort to doing mock interviews with our career staff, to actually figuring out what kind of companies we’d want to work for, to prepping for our tech talks and demo day, and a whole host of other activities. I’ve decided to adopt a very healthy coping mechanism: other than an initial read-through of all of the material we were given, I’m pretending like none of that exists. (For now.)
Come see me talk!
And on a completely different note, if you’re in Austin, I’m giving a lightning talk tomorrow at Women Who Code Austin’s meetup! Come join us for food and camraderie and to hear about my conference experience and count how many times I say “um.” (In college, I actually sought out people who were willing to tally the number of times I said “um” to practice speaking with because that’s a habit I’ve been working on breaking.)
I also forgot how much public speaking occasionally terrifies me. It’ll be fine, right? Right. It’ll be fine. Probably.