YYashika Vijayvargiya·Nov 2Rate Limiting in Rails 8.1: Protect Your APIs Without Rack::AttackLearn Rails 8.1 rate limiting with practical examples. Explore rate_limit, custom responses, user-based limits, shared scopes, Redis, and Rack::Attack.8 min read·railswithyashika.hashnode.dev
JJosef Strzibny·Oct 24RubyLLM 2.x: What's new for your agentsRubyLLM 2.0 and 2.1 bring a lot of improvements to building agents. You can run the agent loop one step at a time, tools can now wait for a human to approve them and agents can live in the database and therefore survive a restart.11 min read·serpapi.hashnode.dev
SSina Rezaei·Oct 8Getting to Know Yourself: Understanding self in RubyLearn how self works in Ruby through objects, scope, and method context.9 min read·sinarezaei.hashnode.dev
YYashika Vijayvargiya·Sep 22Your Rails Transaction Rolled Back. What Happened to the API Call, Email, or Job?Learn why HTTP requests, emails, and background jobs can become unsafe inside Rails database transactions, and how TransactionGuard detects these side effects.10 min read·railswithyashika.hashnode.dev
CChetan s·Sep 15What I learned strapping AI agents onto a nine year old Rails appNine years of Rails kept breaking our AI agents. The fix wasn't a better model, it was a harness: blocking hooks, a lint ratchet, fresh subagents.9 min read·buildstuff.hashnode.dev2AR
SShipeasy·Aug 20Ops queue for agents — turning every failure into a fixable ticketAt Shipeasy, every production signal that matters becomes a ticket that an agent can act on — no human triage in between. Not a log line. Not a Slack message that scrolls past. A first-class work item4 min read·shipeasy.hashnode.dev1
SShipeasy·Aug 20When a build breaks, the bug fixes itselfWe stopped babysitting CI failures. Now a red build files its own bug — and an AI agent picks it up and ships the fix. PROBLEM — A failed build told no one Our CI would fail, and then… nothing would h6 min read·shipeasy.hashnode.dev
ZZeroDrop·Aug 3RSpec Email Testing Without MailCatcherTest signup, OTP, and magic-link flows in RSpec with no local mail server. No MailCatcher daemon, no regex — just real email verification in CI.6 min read·zerodrop.hashnode.dev
JJosef Strzibny·Aug 1Why is Ruby on Rails a great fit for AI agentsRuby on Rails happens to excel at all things that matter in agentic programming. Token efficiency, predictability, and ecosystem ergonomics makes Rails one of the best choice for robots as it once was for humans.24 min read·serpapi.hashnode.dev
JJeremy Longshore·Jul 1Deep Dive Part 1: The Safety Architecture of Letting AI Agents Touch Your Production Rails DatabaseWhen a language-model agent needs to debug a production issue, it faces a dilemma: either it has no access to live data (useless), or it gets a Rails console (dangerous). There is no safe middle groun16 min read·jeremylongshore.hashnode.dev