A self-taught coder's 12 weeks at the Recurse Center

The author, a self-taught programmer based in the UK, writes a first-person account of completing a 12-week batch at the Recurse Center (RC), a programming retreat with a physical hub in Brooklyn, New York. RC runs several 6-week batches a year; participants can apply to do one or, as the author did, two back to back for a 12-week stay. Batches can be done in the hub, fully remote, or hybrid, and the work is self-directed: RC provides faculty, a calendar of activities and support, but there are few pass-or-fail checkpoints.

The author found RC by accident, twice, via links at the bottom of two Hacker News articles, one about 3D-printing an ergonomic laptop setup and one about niche solutions enabled by 3D printing. Only while writing this piece did the author realize both were written by the same person, thanking her by name: Nicole. The first time, self-doubt about being 'computer-sciency enough' as a self-taught coder, and about cultural fit as someone from a council estate in England, stopped the author from applying. Weeks later, dissatisfaction with career progress prompted digging up the bookmarked site and filling in the application.

The application had three stages. First, a written application that went beyond standard form fields into prose questions, which the author read as RC wanting to understand applicants qualitatively rather than just by credentials. Second, an informal Zoom conversation with an RC alum, described as an easy, laughing chat built on shared interests. Third, a pair-programming session, which the author approached with anxiety, having never paired before. RC's own guidance framed this stage as not a test but a way to see how an applicant approaches problems and communicates while collaborating; applicants can pick from suggested exercises or propose their own. The author generalized an existing game engine into a Space Invaders clone for the session, was paired with another kind and supportive alum, and the two worked through a few bugs together in what turned out to be a short, enjoyable session. The author notes the application process itself was valuable regardless of outcome: it clarified their sense of their own story as a programmer, normalized video calls with strangers, and produced a first experience of pair programming.

On culture, the author describes RC as a strongly social environment where applicants are selected for being both capable and kind, where cold-messaging strangers on the team-chat tool Zulip is explicitly encouraged and normalized, and where the mix of people on a batch, some formally trained in computer science, some self-taught, some current students, some educators, tends to cluster around shared interests; the author's own batch leaned toward people drawn to visual or graphically creative work.

Being fully remote brought its own friction, mainly around time zones. RC's core hours run on New York time; from the UK, five hours ahead, that meant a working day from 4pm to 10pm local time, on top of the author's natural habit of waking around 5am. Batch participants are expected to commit to at least 6 hours a day on average, and it took the author about a week to settle into a routine. Even though not required to, the author chose to stay present until 10pm every day for personal discipline, largely succeeding, and avoided scheduling Zoom calls late in the day because tiredness made it harder to bring social energy to face-to-face chats.

On how time is spent, the author describes RC as self-directed: a shared calendar lists daily events, attendance is optional, and faculty step in only if someone appears completely disengaged. Named activities include pair-programming exercises, 'Impossible Day' and 'Impossible Hour' (deliberately attempting tasks expected to fail), group read-throughs of books such as The Book of Shaders, special-interest groups covering audio programming, GPU shaders, systems programming and LLM usage or creation, meta-sessions for reviewing one's own progress, and career planning discussions. The author also mentions 'coffee chats' as a favorite part of the batch, a one-on-one social feature that can be scheduled as often as desired. The supplied text is drawn from parts 1 through 6 of an 8-part series and cuts off mid-sentence inside the coffee-chats discussion; the final parts and any wrap-up of how the batch concluded are not covered here.

Key facts

A self-taught, UK-based programmer did a fully remote 12-week batch, made of two consecutive 6-week batches, at the Recurse Center, the Brooklyn-based programming retreat.
The application process had three stages: a prose-heavy written application, an informal Zoom conversation with an RC alum, and a pair-programming session explicitly framed as not a test.
Discovery came through links at the bottom of two Hacker News articles, both later realized to be by the same author, Nicole, whom the writer thanks by name.
Being 5 hours ahead of New York pushed RC's core hours to 4pm-10pm UK time; participants are expected to average at least 6 hours a day, and the author chose to stay present until 10pm daily for personal discipline.
RC is self-directed: a shared calendar of optional events includes pair-programming exercises, 'Impossible Day/Hour', book read-throughs, special-interest groups (audio programming, GPU shaders, systems programming, LLM use and creation), and one-on-one 'coffee chats'.

Why it matters

Programming retreats and self-directed learning communities are a recurring theme on Hacker News, and this piece is a rare detailed, first-person walk-through of what one, the Recurse Center, actually involves day to day, from the application funnel to the lived experience of a batch, rather than a marketing description of the program.

Who it affects

It speaks most directly to self-taught programmers weighing whether they are 'qualified enough' to apply to a place like RC, to anyone considering a fully remote batch and the time zone tradeoffs that come with it, and to people curious about what self-directed, non-credentialed technical communities look like in practice.

How to use it

The concrete process detail is the useful part: RC runs multiple 6-week batches a year that can be combined into longer stints, can be done in-hub, remote or hybrid, and its application has three stages, a written application, an informal interview, and a pair-programming session explicitly framed as not a test, where applicants can pick or propose the exercise. Remote applicants specifically should expect to compensate for the hub's in-person bumping-into-people culture by actively messaging people on the team-chat tool Zulip and attending events.

How solid is it

This is one person's first-hand account of their own batch, not an independent evaluation of the Recurse Center; the source text is parts 1 through 6 of an 8-part series and cuts off mid-sentence, so the article's own conclusion and any assessment of outcomes after the batch are not included here.

Risks and caveats

The account is anecdotal and specific to one remote, UK-based participant's experience and time zone; RC's culture, workload expectations, and the balance of self-direction versus structure may be experienced differently by other applicants. No dates, batch year, or the author's name are given in the source, and the article's final two parts are not part of the supplied text.

“He who has begun is half done; dare to know, begin!”

— Horace