GoRails Screencasts is a Ruby on Rails tutorial series that works at the level of the individual method. A lesson picks one tool from the framework, explains the problem it solves, and then makes it run inside a small demo app. The demo apps are plain. There is a task list with statuses like urgent, in progress, pending and done, a scaffolded examples model with an optional field, and a post that needs a title and body before it can be published. With so little else on screen, the method gets all the attention. The teaching style is conversational and visibly live. Several lessons open with a casual greeting, code is typed in real time, and the browser gets refreshed to check the result. When something breaks, it gets fixed on screen: in 'ActiveRecord in_order_of', a stray space causes a syntax error that is corrected before the lesson continues. That same lesson lays out a plain Ruby route to a custom order, mapping each status to a number in a hash and sorting with sort_by. Results get checked in more than one place. The normalizes lessons query the Rails console for what was saved and read the server log to show the browser submitting an empty string. 'Clean Up Optional Attributes in Rails with Normalizes' fixes that with a lambda that calls presence, which returns the value or nil, so a blank field is stored as a null rather than an empty string. 'Normalize All ActiveRecord Attributes' refers back to a previous lesson on that technique and adds a second optional field to show the gap left when only one attribute is normalized. Reading other people's code is one way lessons get started. 'valid with Context' opens with a greeting for the new year of 2026 and the view that reading code by more seasoned developers is one of the best ways to learn. It then opens a signup model in Basecamp's Fizzy app, spots validations scoped to a context, and rebuilds the idea around a publish method that checks title and body only when a post is being published. The closing point is that the same context can be passed to save as well as to valid. 'Removing Duplication Using with_options' likewise comes from browsing a codebase, then turns to the Rails API docs to show options merged into every call inside the block, including an example built on associations that share dependent destroy. Community questions feed the series too. 'Dynamic Partial Rendering' takes a question from the GoRails Discord group about type checking in a view, shows Rails rendering partials for single table inheritance models on its own, and uses string interpolation to reach the right edit partial for single-unit and multi-unit properties. It also notes a linter rule the approach runs into and leaves the final call to the developer.