Recurse Center: Expectations

In a few days, on 1/7/2018, I’m going to start a 3-month batch at the Recurse Center. I am beyond excited. I’ve written previously not getting in on my first try, and you may have stumbled on this post while googling everything you could find about RC – I know I did! I’ll be blogging weekly about my journey for the next 12 weeks, so I hope you find this helpful.

In this post, I want to cover what I plan to do, hope to achieve, and expect to experience RC. I imagine I’ll be hilariously inaccurate with my predictions, so this should be fun to read in a few months

Here are my programming goals for Recurse, roughly by priority:

  1. Pair program and learn from others as much as I can!
  2. Get hired as a software developer. The fundamental goal of RC is to help me improve as a programmer. A promise I made myself is that if I dedicated 3 months to this, I’d come out with a career I can depend on (which has been my biggest source of stress for a while). I see getting hired both as a financial imperative, and as validation that I’ve become a better programmer, to the point I can depend on my craft financially.
  3. Gain a deeper understanding of how code works when it’s run. I want to deeply understand what happens from when you run code to the point it becomes machine code. I’ve heard many reasonable explanations for why different languages are suitable for different tasks, but I don’t think I’ll really understand this until I trace how syntax becomes machine code.
  4. Gain a deep, under-the-hood understanding of Javascript (and Ruby, if I have time)  I want to finally go through [YDKJS](, finish [Principles of Object Oriented JS](, learn ES6, dig into Promises, Async/Await. I’d like to get to a point where I can, for example, make sense of how [Vue reactivity]( works.
  5. Learn design patterns, and practice data structures and algorithms. I think there are usually study groups that form at RC to do this, so I’m excited to explore with fellow Recursers.
  6. Learn a new language with a new paradigm: Scala, Rust, Go. Both my RC interviewer and alums I’ve spoken to gave me the advice to learn something with a _totally different_ paradigm from what I’m used to.
  7. Stretch goals: use D3.js, build a project using the [WebAudio API](, build a MacOS app with Electron or Swift, learn React and build a small Rails app. I really don’t think I’ll have time for these things, but who knows!

Here are things I expect to be hard:

1. Learning so much complex information in a dense, short period of time
2. Learning to work with people from multiple backgrounds/communication styles
3. Prioritizing what exactly I should work on on a daily basis
4. Balancing my own projects with collaborating with other people
5. Prepping for interviews and learning algorithms and data structure questions
6. Balancing writing code with learning from/socializing with others
7. Writing and thinking about code 8-10 hours a day, non-stop

Here are things I’m really looking forward to:

1. Collaborating and learning from engineers from all walks of life
2. Being in a supportive, welcoming environment geared towards learning
3. The constraint of solely focusing on code for 3 months
4. Learning material that I’m genuinely excited to learn, and knowing that my trade can reward me with financial stability.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s