Email is one of those features every app eventually needs and nobody particularly wants to build. Welcome emails, password resets, weekly digests, transactional notifications — the list grows quickly once your app is

Speaking at a tech conference is one of those career milestones that seems impossibly far away until someone tells you the actual submission process, at which point it becomes merely uncomfortable. The secret

Arrays in Ruby can be nested arbitrarily deep — arrays of arrays of arrays. flatten collapses them into a single level, but knowing when to flatten fully versus partially is what separates clean

Ruby’s GIL — the Global Interpreter Lock — has been the punchline of many conversations about concurrency for a long time. The lock means that even with multiple threads, only one can execute

File uploads have a reputation for being one of those features that look simple and turn out to be a multi-day project. Pick a storage backend, configure credentials, handle direct uploads, generate variants,

The phrase “contribute to open source” carries a weight it doesn’t deserve. Somewhere along the way it became synonymous with submitting a pull request to a major framework, getting accepted by Matz himself,

Sorting a collection of hashes by a single key is straightforward, but sorting by multiple keys — primary sort by one field, secondary sort by another — requires a slightly different approach using

If you’ve been writing Ruby for a while, you’ve probably cobbled together something to represent simple value objects — a Struct, a frozen hash, maybe a plain class with an attr_reader and a

Turbo handles navigation and real-time updates beautifully — page transitions, stream updates, frame replacement, all without writing JavaScript. But there’s always that next layer of requirement: a dropdown that opens and closes, a

Most developers I know are suspicious of “building an audience.” It sounds like something that requires a ring light, a content calendar, and a willingness to perform enthusiasm for things you don’t actually

Most Ruby developers have a complicated relationship with concurrency. Threads feel dangerous. Processes feel heavy. And the GIL — the Global Interpreter Lock — has been the villain in so many horror stories

For years, the default answer to “how do I run background jobs in Rails?” has been: add Redis, add Sidekiq, configure two separate services, monitor two dashboards, and don’t forget to handle Redis

Most developers treat their GitHub profile like a filing cabinet — a place to dump code and move on. They’re not wrong to use it that way; that’s technically what it’s for. But

Pattern matching landed in Ruby 2.7 as experimental and graduated to stable in Ruby 3.0. Most Ruby developers have heard of it; far fewer use it confidently in production code. This post cuts

Real-time features used to mean reaching for ActionCable, writing JavaScript event listeners, and managing WebSocket state that lives entirely outside your Rails stack. Turbo Streams changed that equation entirely. Built into Rails 7