November 13, 2016
The Week By the Numbers:
Cups of coffee had: 4
Miles ran: 5.25
Current length of to-do list: 32
Hours spent in front of a computer: more than I’d like to admit (I didn’t actually keep track of this, but I think it’d be interesting and/or possibly slightly terrifying)
The running theme this week was back-end work: Node, Express, and SQL. Most of my work in the past has been entirely on the front-end, with a week of learning back-end on my own right before Foundations started. It’s an entirely different side of things, but I really enjoy it — most of the time. It can be sometimes be really frustrating being unable to see the changes that you’re making without console logging everything, but I like the unique challenges that it presents. (Although I did go back to my Game of Life on Saturday night purely because I needed a small break from the back-end altogether, and just wanted to go back to making pretty colors go certain places for a bit.)
Pairing this week was a somewhat interesting, and different, experience for me. I felt like a couple of the people I paired with in the first week were more comfortable with the material than I was, so I was the one who needed to slow my pair down occasionally to really grasp what was going on. This week, I felt like I had a better understanding of the material than some of my pairs, and so I felt like I did more explaining than I did last week. This far from a bad thing; teaching someone else definitely forces you to really know what you’re talking about, and I discovered in some of those cases that I didn’t understand something as well as I thought I did. In other cases, it really cemented the concept in my mind, and I was able to more clearly think through and articulate solutions.
One of the things I need to try to do better going forward is time management and prioritization. It’s not that I waste a lot of time (I’d like to think that four years at Rice made me very efficient with my time), but there’s just a very long list of things I want to do regularly and unless I make them a priority and make an effort to actually do them, they won’t happen. There are a few (just like my to-do list, this list is also growing) personal projects that I want to build, and I haven’t really reserved any time each day to do so. Likewise with Code Wars: I’ve used our hour in the morning sometimes to work on the challenges, but sometimes I opt to do other things, like finishing up the previous day’s blog post or reviewing for the upcoming day’s lecture and workshops. I also missed a meet up last week that I had been wanting to go to because I convinced myself that I was too tired and that I wanted to study — which I’m a little sad about.
Besides the time machine that I’m planning on building as my capstone project, I haven’t yet found a good solution or system to be able to accommodate everything I want to do. I hope to sort out some of those things this week and start establishing a system, now that we’re in a little more of a rhythm.
The Fullstack & Remote Experiences
I’m no longer referring to this section as just “the Remote Experience,” because I feel like what we’ve been experiencing transcends that — I’m not sure anybody in our cohort denies that we’re really getting the Fullstack experience.
To start, quite possibly one of the biggest events in our lives happened this week — the election of Donald Trump to the American presidency. Instead of glossing over it and pretending like it was a typical Wednesday the day afterwards, Fullstack made some time in the day to allow us to openly discuss amongst each other our thoughts and feelings and hopes and fears, without any mention of code whatsoever. I enormously appreciated Fullstack’s commitment to creating an open, non-judgmental, safe environment for every single student, whether in New York, Chicago, or online. The “Ladies of Fullstack” group has also been a great support system — sometimes, it’s just really nice to be among a group of women.
In other news, Pieter DePree, Recruiting Lead at Stack Overflow, came to campus to talk about how Stack Overflow hires developers, and more specifically, what we can do to start preparing ourselves and our online presence for the job hunt in a couple of months. Though some of his points didn’t necessarily apply at this point in time, it did make us aware of what we need to start doing when, and gave us the knowledge of how to prepare ourselves for when it did. It was also really interesting to get a detailed look into the hiring process at company like Stack Overflow.
And lastly, who could forget about our Minecraft adventure on Friday? I’ve written a bit on it before, so I’m not going to repeat any of it here, but I felt like that was a great bonding moment for our cohort and everyone associated with it — instructors, fellows, staff, and even one of Fullstack’s co-founders. I haven’t yet been back into our server to see if people have built anything this weekend, but I’m excited to check in later tonight and see what’s been happening.