User’s Manual

Welcome to an unusual experiment

The Recurse Center is unlike the rest of the world. This guide is designed to help you get settled in and get the most out of your time here, and is written for people who have been admitted to RC or are attending a batch.

One of the things that makes the Recurse Center different is that it's largely self-directed. This means that while you’re here, you won't have someone telling you what to do or how to approach your time. We don’t have grades, exams, curricula, or even classes, because we believe that people learn best when they have the freedom to explore what most interests them.

This doesn't mean the Recurse Center is a vacuum, just that the structure we provide is optional, not mandatory. We've been running the Recurse Center since the summer of 2011, and we've learned a good amount about what strategies have and have not worked for different types of people in the past.

The structure we do provide is shared space and time: you’ll be doing a batch alongside other like-minded programmers from a tremendously diverse set of backgrounds, and in joining RC you’ll be joining a community of over 2,700 people who have done a retreat. We only ask that you commit to RC full time, and that you work on open source software while you're here (i.e., don't work on proprietary code or code that you couldn't pair on or share with others).

The environment

Regardless of whether you attend online or in-person, the core of RC is the same. You should check out our About page to learn more about the experience.

The self-directives

What should you actually do while you're at RC in order to grow and learn the most?

The answer to this question is summed up in three guiding principles called the self-directives. They are:

• Work at the edge of your abilities
• Build your volitional muscles
• Learn generously

We recommend that you think about how to apply the self-directives to your time at RC before your batch begins. Doing the self-directives looks different for everyone, but here are some tips to get you started:

• If you’re tackling a big project that’s at the edge of your abilities, you might feel stuck sometimes. As one alum put it, try to have ‘brain work’ — bigger, challenging stuff that requires deep focus — and ‘finger work’ — smaller implementation work you can turn to when you need to rebuild momentum.
• When considering the big picture of what you want to work on at RC, pay attention to what makes you most excited. Do you get butterflies thinking about a specific project or avenue of inquiry? Go for that! And remember: it’s okay to change course if what you’re most excited to do changes. During your batch you’ll encounter lots of new people and ideas. Building your volitional muscles means building your capacity to make decisions about what you do based on your motivations, and it’s an ongoing process, not something you do once in your first week.
• Share what you’re stuck on. We have lots of ways for you to share what you're working on, and we encourage you to celebrate victories! But it’s also important to ask questions and express uncertainty in public: it’s highly likely someone else is struggling with the same thing you are, or struggled with something similar in the past. Posting on Zulip or sharing a bug that’s besting you in check-ins or presentations will help you get advice and new perspectives on your problem.
• Pair program. This is a great way to do all three of the self-directives. See the next section for more about that!
• When in doubt, program. The more code you write at RC, the more you’ll learn. Don’t worry about choosing the “perfect” project before you begin. It’s much better to just start programming something, anything, that you’re excited about. Even something that feels small can help you build momentum.

Pair programming

One of the most valuable ways to do all of the self-directives at RC is by pair programming. Most alums wish they'd spent more time pair programming during their batch. We learned this after the second batch, and have shared this fact with every batch since. Despite this, lots of people still tell us after their batch that they really wish they'd paired more.

What is pair programming?

Pairing means two people working on the same code using a single computer, either via screensharing on a video call or by sitting next to one another. Using only one computer is important, because pairing is about actively collaborating and not just two people working on the same project or sitting next to each other on their own computers.

Pairing quickstart guide

Finding someone to pair with

The best way to do this is to share what you’re working on regularly! That will help people find you. Check out the checkins channel on Zulip to learn about what people are working on, and don’t be afraid to reach out if something sounds interesting. Check out more specific interest channels on Zulip, too, especially the pairing channel, where you can look for pairing buddies. In both the virtual and physical spaces we have designated pairing stations: you can use them to pair, or you can work at one by yourself to signal that you’re open to pairing.

Finding someone to pair with

It's good to make sure you have similar (or at least compatible) goals before you start pairing. If one person thinks the goal is to learn Python, and the other thinks the goal is to fix a bug as quickly as possible, you can run into friction. Make sure you're on the same page, or at least know where each other are coming from.

A common way to pair is having a "driver" and a "navigator": the driver is the one actually typing the code. The navigator sits next to the driver and reads the same screen, and is there to talk through ideas, direct the driver, and think about how the code currently being written fits into the larger project. If you're pairing this way, try to switch it up sometimes: switching regularly helps with knowledge transfer, ensures that both people get to drive and know what's going on, and helps keep everyone energized.

Getting through tough spots

Pairing can be hard at first, especially if you haven’t done it before. You may not think you have any code that is pair-worthy, or any valuable experience to contribute. It might feel uncomfortable programming out loud. You might not be sure if anyone shares your specific interests. But if we can give one piece of advice most strongly from our own experience and that of the thousands of Recursers who came before you, it’s that it’s worth pushing through these challenges.

Why we love pairing

There are several advantages to pairing. One is that it keeps everyone focused on the task at hand. When you're working alone, it can be easy to get distracted (e.g., by email or a shiny new JavaScript framework), but it's much, much harder to switch to Gmail when someone's sitting by your side and also reading your screen. Successful pairing should yield a productive feedback loop where each person helps keep the other focused.

Another advantage is that the navigator can catch a lot of small errors immediately (typos, missing semicolons, incorrect variable names, etc). It's faster and easier to fix bugs the moment they're introduced than at any subsequent time, so this ends up being a big win. Plus, as the saying goes, with many eyes, all bugs are shallow.

Pairing can help with everything from learning a language to picking up editor or command line tricks. And it’s motivating: it can get you excited about your project, stay with a problem when you might otherwise get distracted, or allow you to take on projects of a bigger scope than you could alone. Working on something deeply together can be a rare and special way to connect with another person.

Oh also, it's fun!

For all these reasons and more, pairing is one of the best ways to practice all three of the self-directives. We think everyone should try it — at least a few times and a few different ways.

The social rules

We have a small set of lightweight social rules that make more explicit certain social norms that are normally implicit. Most of our social rules really boil down to "don't be a jerk" or "don't be annoying." Of course, almost nobody sets out to be a jerk or annoying, so telling people not to be jerks isn't a very productive strategy. That's why our social rules are designed to curtail specific behavior we've found to be destructive to a supportive, productive, and fun learning environment. The social rules are:

No feigning surprise

You shouldn't act surprised when people say they don't know something. This applies to both technical things ("What?! I can't believe you don't know what the stack is!") and non-technical things ("You don't know who RMS is?!").

No well-actuallys

A well-actually happens when someone says something that's almost - but not entirely - correct, and you say, "well, actually…" and then give a minor correction. This can be very disruptive when the correction has no bearing on the crux of the conversation.

No back-seat driving

If you overhear, or read on Zulip, people working through a problem, you shouldn't give advice unless you’re actively participating in the conversation.

No subtle -isms

Our last social rule bans subtle racism, sexism, homophobia, transphobia, and other kinds of bias. Subtle -isms are small things that make others feel unwelcome, things that we all sometimes do by mistake.

You should read more about the social rules here, including how to gracefully handle it when you unintentionally break them. These rules are designed to help all of us build a pleasant, productive, and fearless community.

Code of conduct

The social rules don't cover harassment or discrimination. For that, we have a code of conduct enforced by the RC faculty. All members of the RC community are expected to abide by our code of conduct.

You can report code of conduct violations using our reporting form.

Logistics

The time commitment

Our core hours are Monday through Friday, 11 am to 5 pm ET, with many additional events outside of those hours. We don't track attendance down to the hour, but we will check in if we don't see you for a day. Our expectation is that RC is your primary commitment while you're in batch, and that you're committing to joining us during our core hours for the entirety of your batch.

RC doesn’t work well for people who aren’t ready to make a significant commitment to it. We say six hours a day, but that’s a proxy for the commitment we expect you to make rather than a strict requirement in itself. It’s difficult to impossible to do RC when you have a full-time or part-time job, or are going to school, and we expect that anyone attending a batch will not have any other significant commitments.

We’ve seen people try to juggle classes and part-time work with RC, and they invariably end up getting less out of the experience than they want to — most wind up leaving their batches early.

If you miss the first day's orientation events, we'll ask you to join a later batch. If we notice that you aren’t participating in your batch, we’ll reach out to you, and may ask you to end your batch early. If you're unable to continue doing RC full-time, see the ending your batch early section below.

Batch length

Regardless of the batch you apply for, if you’re admitted to RC you’ll be able to confirm for any open batch and will be able to choose to commit to six or 12 weeks. If you’re unsure of whether you’ll be able to attend for the full 12 weeks, confirm for a six-week half-batch: you have the option to extend to 12 weeks at any point during your batch if you let a faculty member know you’d like to.

If you need to shorten your batch, that’s okay — again, let a faculty member know. We would much rather hear that you’re struggling to participate or need to end your time at RC early than notice you’ve stopped participating and have to track you down!

Advice

Before RC

Taking time out of your usual routine to attend an RC retreat is an exciting and sometimes daunting prospect. The Recurse Center is as much a social hack as anything. You spend a few months on your own somewhere, programming solo for its own sake, and that's what many Recursers were doing right before RC. Here you'll have the accountability, momentum, and inspiration from a group of peers who care about building and learning as much as you do. (And you'll have an easy answer for your friends and family when they ask what the heck you're doing with your life.)

Pre-batch onboarding focuses on helping you introduce yourself to the RC community and our tools, and meet your batchmates. You’ll get an invite to Zulip, our chat software, before your batch. You should introduce yourself there, and choose some channels to subscribe to. If you’d like to learn more about how Zulip works, you can read the docs.

Look for the orange events on the RC calendar — those are your orientation events! You must attend the first day talks on the first day of your batch. You can come to as many of the other orientation events as look interesting to you (ideally all of them).

Look at the Directory to see who's in your batch, and add a photo and bio on your settings page. After you check out who else is in your batch, think about what you might like to work on, and who you’d like to meet and pair with in your first few weeks.

And finally, if you’re attending remotely, adjust your workspace a little bit to change your context: change where you sit, add a little plant to your desk, or rotate your workspace.

During your batch

Your first two weeks

Your first day will kick off with a series of welcome talks and meet and greets. The first day events are an important part of your batch, so don’t miss them! If you do, we’ll likely ask you to attend a later batch. We’ll talk about RC, the self-directives, and the social rules, and there will be lots of time to get to know your fellow Recursers.

The first week will be full of fun events for meeting people, learning about what they’re working on, and sharing your own ideas. Here’s some advice for your first couple of weeks to help you get into the swing of things.

Meet people!

Get to know your batchmates! The more you invest in building relationships at the beginning, the more you'll be able to take advantage of being surrounded by so many kind, smart, ambitious people who are excited to learn together.

How? Sign up for coffee chats, attend events you find on the calendar, and reach out to people who have similar interests.

Choose an accountability mechanism and then commit to it.

At RC, you’re primarily accountable to yourself. You’re setting your own goals, working and learning at your own pace, and following your curiosity.

Making your goals and progress public gives you room to reflect on what you’re doing and why, support from your batchmates, and (if it’s written) a record of what you’ve done at the end of the batch. Writing or talking about what you’re working on helps cement it for you, and can help you see possibilities and pitfalls you otherwise wouldn’t. This kind of reflection is at the core of building your volitional muscles.

How? Posting checkins on Zulip, attending daily checkins, coming to office hours on a regular basis, pinging a friend at the end of every day, committing to giving a presentation, blogging, or setting up your own sort of structure.

Create the context you need to do good work.

Our hope is that you’re able to fully immerse yourself in RC during your batch by separating this time from the rest of your life. A big part of this immersion comes from the context you put yourself in.

You might have experienced a state of flow while you worked in the past: you have momentum, you’re super focused, the minutes fly by, and the difficult things aren’t easy but they don’t stop you. The feeling has a lot in common with excitement, and if you can get into it, we think it’s the optimal state to do RC in.

This extends beyond your physical environment. What do you need to tell yourself about what you’re doing — why are you taking the time to do RC? Remind yourself as often as you need to. Are there friends or family members who aren’t sure about you taking three months away from work or other obligations to do RC? Take the time to have those conversations, so you have their support.

If you find yourself struggling to do a certain kind of work, you can also ask yourself what kind of work you are in the mood to do. Maybe you’re trying to force yourself to do a Leetcode problem when what you really want to do is something inspired by an event you went to earlier in the week.

How? If you have experienced flow before, think back to it. What mood were you in? What was the space you were in like? What time of day was it? Try to recreate the situation, and see what happens. If you haven’t, pay attention to and try to adjust your environment, keep programming, and see what you learn.

Say no to something.

You’ll come into RC with a rough plan or goal for your time, and you’ll likely encounter more things than you have time to do in your first week. That makes it necessary to decide what you will and won’t spend your time on.

But treating time as a scarce resource makes it scarcer: if you try to over-optimize or overthink, that will take time away from your work! Simplify things for yourself. Say no to the stuff that you feel you should do, but that isn’t intrinsically exciting to you.

How? You’ll likely sign up for a lot of social things in your first week (it’s encouraged!) – things like pairing sessions, social events, and working/study groups. You may then need to step back from some of them to balance your working and social time. Take stock of how you feel on day one of week two, and say “no” to the things that aren’t serving you.

Do one challenging thing, and then do another.

This is a concrete way to ‘check’ if you’re working at the edge of your abilities. The reason to work at the edge of your abilities is to incrementally grow what you’re capable of at RC. You’ll do that by doing work that’s challenging one day, then waking up the next and doing the same.

How? Ask yourself if what you’re working on is the right level of difficult where you’re learning something new. Challenging doesn’t mean impossible: the edge of your abilities is a sweet spot of difficult but motivating. If you’re pleasantly surprised by the work you’ve done at the end of a week, it’s a good sign.

A checklist for getting started:

• Create a recurse.com account and fill out your profile on the Directory
• Log in to Zulip and introduce yourself in the welcome stream
• Sign up for coffee chats
• If you’re coming to the Brooklyn hub, see hub details for important space-related notes
• Get settled in your physical environment
• Make a desk on Virtual RC if you’re attending an online batch, or pick a cubby if you’re attending in-person
• Choose an accountability mechanism, whether that’s in-person or Zulip checkins, blogging, or something else
• Attend presentations
• Check the calendar and RSVP to events you’re excited about
• If there’s an event you wish existed but doesn’t, create it!
• Set your intentions/goals for the retreat and plan what you’d like to work on
• Share what you’re planning on working on widely and often to find others who are interested in similar things

The midpoint of your batch

Whether you’re doing a six- or a 12-week batch, halfway through is a great point to stop and reflect on how your batch has been going. Take some time to think about whether or not you’ve been working at the edge of your abilities and about your goals for the remainder of your batch. You may need to change your plans multiple times – that’s normal. Setting and resetting your expectations for yourself will encourage you to keep learning.

If you’re doing a twelve week batch, this is when one batch ends and another begins. You’ll have to say goodbye to some of the people you’ve been learning and working with in your sixth week (don’t worry – you don’t really have to graduate). You’ll also be saying hello to lots of new people in your seventh. Try to attend the first week events so that you can meet your new batchmates and find new collaborators!

If you are thinking about using RC’s career services we recommend reaching out to a career facilitator in the latter half of your batch on Jobs Chat.

The end of your batch

When your batch ends, you’ll “never graduate,” which means that you’ll become an RC alum. We have a ceremony on your last day where you’ll be able to get your t-shirt and a collection of kind words your batchmates have sent to you.

Alums are still very welcome to participate in RC when they’re not in batch, and many do: as an alum you can attend any event you like in Virtual RC, pair program, participate in conversations on Zulip, run events, present at presentations, apply for another batch, recommend friends, and so on.

Ending your batch early

If your circumstances change and you can’t or no longer want to participate in RC before the last day of your batch, please let us know you’d like to withdraw from your batch. It’s helpful to us if you let us know why you’re withdrawing and we may ask to have a short conversation with you to learn more about your decision. We’ll let you know how to best communicate your change of plans to the rest of your batch, and we’ll deactivate your accounts on Zulip and recurse.com until you return for another batch. If you’re an alum and you’re withdrawing from a batch that isn’t your first, we’ll remove you from your current batch but we won’t deactivate your accounts.

Please reach out to us as soon as you can. We value clear, proactive communication, which saves us time and energy checking in with you and hopefully also saves you some guilt and anxiety. This is not a regular school or job, where you face discipline for “failing.” We view honest self-reflection and discernment positively. If you need to withdraw from the batch you’re attending, you’ll be welcome to confirm for another batch that begins within six months, or to re-apply in the future.

Jobs

RC makes money by recruiting. We see recruiting and education as integrated parts of a whole, each of which gets better as the RC community gets bigger, more diverse, and more active.

Recruiting is a lifelong service for Recursers – we’re a resource during your batch, after, and even years into the future.

To learn more about getting a job through RC, you can read our jobs advice and get in touch with us on Jobs Chat. Here’s what we offer:

• We’ll work with you to understand what you’re looking for and your goals, and provide personalized recommendations for roles with our partner companies
• We'll only connect you with companies you’re genuinely interested in
• We’ll be here to help guide you throughout your interview process and provide advice, be a rubber duck, help craft communications, and help you negotiate
• We can connect you to alumni mock interviewers who are experienced at giving tech interviews, so you can practice before the real thing
• We can connect you with alums at companies to help you learn about what it’s like working there.

We have partnerships with over 100 companies who pay us to hire Recursers for programming jobs.

If you’re hired by a partner company, they pay us a fee (usually 25% of your first year salary) provided you stay at the company at least 90 days. This fee is paid out of the company’s recruiting budget and does not come out of your salary. There’s no obligation to get a job through RC or to only interview at RC partner companies but it’s worth noting that recruiting fees are RC's only source of revenue. If you are interested in a programming job after your batch or at any point in the future, please get in touch!

Want to hire from RC?

Some of our best partnerships have come from introductions Recursers have made. Learn more about how to get your company to hire from RC (not a Recurser? Learn more about hiring from RC here).

Jobs software

• Jobs Chat: A private jobs dashboard where you can chat with RC faculty to keep track of the companies you're interviewing at or considering.

• Jobs profile: Update your jobs profile to share your background, projects, skills, and work preferences with companies.

• Company browser: Browse and research companies RC works with.

• Jobs settings: Set your visibility and contact preferences for companies.

Advertising jobs to the RC community

Please don't post job listings for programming roles on Zulip or Community. This makes it harder for RC to succeed as a business and adds to the noise on our forums.

The one exception to this policy is the contracting stream on Zulip, where you're welcome to post about freelance and part-time contracting work, as well as internships, since RC only recruits for full-time jobs.

If you’re an alum working for a company we don't recruit for, we also ask you not recruit Recursers to work with you. If you work at a non-RC company and would like to start recruiting Recursers, or if you work at an RC company and want to know how you can help hire more Recursers, please email us.

Contact information & employee hours