This is the first in a series of posts to record and reflect on my experience at Recurse Center(RC) in NYC (now virtual). Posts will focus on what I’m doing, how I’m doing it, and the effects of those choices on my learning and enthusiasm. Neither length nor polish is important.
Today was a good day. I attended orientation and enjoyed meeting fellow Recursers from different batches—I especially liked Zoom breakout sessions, which I hadn’t encountered before. More experienced Recursers were generous with their advice and people seemed genuinely jazzed to be creating and participating in this community (despite being forced to retreat from the physical RC space). That’s unique.
Beyond getting up and running on internal tools and gleefully exploring the virtual map of RC’s Brooklyn space—with virtual chat rooms replacing their physical manifestations—I began digging into my own learning.
Putting an hour into my BigQuery utility for automatically unnesting tables was one of my top goals for the day. I spent around 1.5–2hrs working on git configuration and reading git documentation, which is not what I was expecting to do. It was useful and productive nonetheless. Taking time to slow down, thoroughly read documentation, and explore learning tangents is a major reason I’m at RC. (At least, that is how I see my RC goals now.) One area of improvement for me is learning to better use basic software engineering tools such as git, sublime, and shortcuts on my mac (as well as improving my typing speed and accuracy). I made progress today. What I intended to do (allow my program to accept passed arguments from the command line) will have to wait till tomorrow.
After chatting and hacking for a few hours, I was feeling a tired, so I shifted to a less mentally tasking activity—watching the introductory lessons of my free introduction to Software Architecture & Design on Udacity. My timing was great. The shift gave me new energy and a feeling of freshness.
As I worked through the short lectures, I did some googling around for additional explanation of topics covered. I enjoy this approach. It mades me feel like I’m investing in the material and owning my learning. I cracked open a fresh notebook and began to scribble my findings. The notebook will be dedicated to this course until I finish. I find the notes more useful if they are contiguous instead of interspersed among random bits and snippets.
Beyond my learning approach, I’m disappointed that the class is geared towards Java programmers. But I’m thinking I can just complete all the exercises in Python without missing much. Fingers cross that pans out.
This post is already longer than I intended, so I’ll wrap up. Till next time.