learn-ruby: one self-taught developer's ordered path into Ruby and Rails

A path, written by the person who walked it

The opening line sets the tone. This road map has helped me as a self-taught developer, and the hope is that it helps you too. That framing matters, because the repository is not a catalogue of everything about Ruby, it is one person's ordered route through the subject, and the site it publishes to is letslearnruby.com. The structure of the file is a table of contents with six bands: Preliminaries, Basics, Foundations, Front end, Advanced Ruby and Rails, and Miscellaneous. Inside those bands the entries are checkboxes, most of them already ticked, which makes the list read as a record of completed work rather than a wish list. The Miscellaneous band is the part that shows the author's range, with entries for the community, for Ruby that is not web development, and for Rails codebases to study. The repository itself is almost empty, a README and a.githooks directory, because the artefact is the document. A broken link gets an issue, and the request is to open one.

One resource if you want one, and why Ruby at all

The Preliminaries section answers the first question a beginner asks, which is the best single learning resource. The answer is the free Odin Project, suggested if you are looking for one resource that can take you from zero to potentially hireable, and the instruction is to keep reading if you want more variety and more depth on certain topics. The second preliminary is the personal one, and it is the most honest paragraph in the list. The author initially looked into full-stack JavaScript, but the JavaScript ecosystem was confusing to them as a solo learner, and they found Ruby to be more straightforward and enjoyable. That is the whole argument for the language in two sentences, and it helps to notice what kind of argument that is, a report of one person's experience rather than a comparison of ecosystems. For a reader who has already chosen Ruby, that section has little to offer, but for someone choosing a first stack it is the most useful paragraph in the file.

Front-end basics come before Ruby basics

The ordering starts with the web itself, which is a deliberate choice. The front-end basics entry points at the Odin Project foundations path, at MDN's web development learning area, and at web.dev, so you can pick one. The second entry is a project, build a blog from scratch, and the recommendation for how to host it is GitHub Pages, with the specific instructions to choose the Project site option and then Start from scratch. That is a deliberate constraint on the toolchain, because a static site hosted on GitHub Pages is the cheapest possible first deployment and it forces you to understand HTML, CSS and a bit of JavaScript before a framework starts hiding them. The list treats this as a prerequisite rather than a parallel track, and that is a reasonable position for a curriculum aimed at someone who has never shipped anything.

Ruby basics with books, videos, exercises and something to build

The Ruby basics section is arranged by learning style, which is the most useful editorial decision in the document. If you want a course, there is the Odin Project Ruby path. If you prefer video, GoRails Ruby for Beginners. If you like an interactive approach, Try Ruby and BigBinary Academy. If you prefer a book, Eloquent Ruby, second edition. Guided practice follows, with the Exercism Ruby track and Advent of Code, with the tip to work alongside other people's Ruby solutions to compare against, and the author's own Advent of Ruby gem as one way to do that. The object-oriented programming entries are Sandi Metz's Practical Object-Oriented Design and 99 Bottles of OOP by Metz and Katrina Owen, and both are marked as paid, which the list signals with a small money symbol. The section closes with build-something suggestions, a command line application, a game where a text based one is the most straightforward and graphical options need Ruby game engines, and a static site with Bridgetown, which the list notes is simpler than a Rails web application and comes with its own Discord server.

Rails basics means building throwaway apps and writing about them

The Rails section opens with a piece of advice that the rest of the list follows. Only books and courses are listed, but be sure to build things as you learn, and the author's method was to build a bunch of little throwaway apps and write about each learning experience, with four of his own write-ups linked from that paragraph. The resources are an interactive quick start, Getting started with Rails, a typecraft playlist for Rails New, GoRails for building a blog with Rails 7 if you like videos, and the Odin Project Rails path. The emphasis on writing about each app is the part that generalises beyond Rails, since it is the same habit the author applied to the Ruby section and it is what turns a tutorial into a portfolio. The list also keeps a note that only books and courses appear here, so a reader looking for a Rails codebase to read will not find one in this section.

Testing advice with a warning attached

The testing entries carry the most specific technical advice in the visible part of the list, and one of them comes with an instruction not to follow it. The recommendation is thoughtbot's Testing Rails, with a note to ignore the controller specs in the book because they have been superseded by request specs, and a link to a summary blog post for people who do not want to read the book. The second entry is Effective Testing with RSpec 3, which is marked as a paid resource. Below those there is a commented out block for minitest links, where each one is annotated as work in progress. That block repays reading even though it is inactive, because it shows the list being maintained rather than frozen, and because the minitest options are the ones a reader on a default Rails stack would actually reach for. The rest of the Rails basics section is two loose entries, a beginner's guide to Ruby on Rails performance and a link to style guides for Ruby, Rails and RSpec at ruby.style.

What the list is, and what to check before following it

Three things about the project matter before you start working through it. First, it is a personal curriculum rather than a survey, and its ordering and its occasional strong opinions are the point, so if you disagree with the sequence the list is not for you and you would be better served by picking a framework and a course. Second, some entries cost money, and the list marks them, which means a learner without a budget has to plan around them rather than discover it halfway through. Third, the resource list is not frozen. The last push was on 2026-10-05, the repository is not archived, and the checked entries show an ongoing process of working through the plan. The licence is recorded as unknown and the repository holds no licence file beyond the README and the githooks directory, which is a small thing to check if you intend to republish the list inside your own curriculum, and there are no GitHub releases, so the document is tracked in the branch rather than in versions.

Editorial conclusion

learn-ruby fits a self-taught developer who has already decided on Ruby and Rails and wants an ordered list rather than a catalogue, and it fits a mentor who needs a curriculum they can hand to a student, since the ordering and the reasoning are already done. It is the wrong choice if you want a survey of the Ruby ecosystem, because the list reflects one person's path, with a small number of strongly held opinions, and it is a poor fit for a team that needs books and courses the organisation has already licensed, since paid entries are marked as such. Before you follow it, check which resources your organisation can actually buy, and read the sections on advanced topics and on Ruby outside web development, since the visible part of the list stops at the Rails basics.

Frequently asked questions

Official sources

1. fpsvogel/learn-ruby on GitHub
2. Issues
3. Project website
4. README