You have six terminal tabs open: server, console, test watcher, logs, git, and one you’ve forgotten the purpose of. Your laptop restarts for an update and all six are gone, along with the

Ruby has quietly accumulated a set of shorthands over the 3.x series — numbered block parameters, hash value omission, rightward assignment, anonymous argument forwarding. Each removes a small amount of ceremony. Adopted carelessly

Every Rails app reaches the point where it needs a cache store, and the reflex answer has been Redis for a decade. Solid Cache challenges that by putting the cache in the database

Ruby 3.1 shipped debug in the standard library, and it quietly made three gems unnecessary. No byebug, no pry-byebug, no version conflicts between them, and — the part that changes how you work

Hashes are the workhorse data structure of most Ruby applications — API responses, configuration objects, parameters, aggregations. Ruby’s Hash class has been steadily gaining methods that reduce the boilerplate of common transformations. transform_keys,

Rails routing gets treated as the part you set up once and forget. For most CRUD resources, resources :posts and moving on is exactly right. But as applications grow, routing decisions start to

Code review is one of the highest-leverage activities a developer does. A good reviewer catches real problems before they reach production, helps less experienced engineers grow faster, and raises the quality bar for

Ruby’s Enumerable module has been quietly gaining methods that make common collection operations more expressive without adding complexity. filter_map alone replaces a pattern that every Ruby developer has written dozens of times. Combined

Turbo Streams are the part of Hotwire that makes Rails feel genuinely modern for collaborative, real-time features. Where Turbo Frames handle navigation and scoped updates on the current user’s page, Turbo Streams broadcast

Most developer LinkedIn profiles are either a digital resume with bullet points copied from a Word document, or a ghost town that hasn’t been touched since the last job search. Both miss what

String manipulation is one of those areas where developers develop habits early and rarely revisit them. split, include?, gsub, strip — these cover a lot of ground. But Ruby’s String class has methods

Database transactions are one of those topics where knowing the basics is easy, but knowing when the basics aren’t enough is harder. ActiveRecord::Base.transaction wraps database operations in an atomic block — either everything

Burnout in software development doesn’t usually announce itself. It accumulates. The work that used to be interesting stops being interesting. You spend longer on tasks that used to take no time. You feel

Ruby methods are first-class citizens in a way that most developers don’t fully use. You can grab a method as an object, pass it around, convert it to a proc, unbind it from

Concerns are one of Rails’ most polarizing features. On one hand, they’re built-in, well-supported, and solve the real problem of reusing code across models and controllers. On the other hand, a codebase full