Rubydex linter lets teams write cross-file, project-level structural rules. Shopify used it to convert long-running tests into 20+ rules that validate the whole codebase quickly.
Rubydex linter performs structural, cross-file checks that single-file linters cannot, e.g., preventing conflicting mixins across inheritance chains.
Shopify replaced many long-running tests with 20+ Rubydex rules and can now lint its monolith in under a minute.
Structural linting is suited for large codebases where architectural constraints span multiple files and inheritance or indirect inclusion makes single-file checks insufficient.
Some highlights: ▶️ Matz's "Meet Spinel" keynote – It's in Japanese, but the English subtitles are good. ▶️ Twenty Years of JRuby – Charles Nutter's keynote on two decades of keeping Ruby thriving on the JVM. ▶️ Surviving Black Friday: 329 Billion Requests with Falcon – Falcon's author Samuel Williams and fellow Shopify engineers on running the Falcon high-performance web server at scale.
Converting a Block Interface to start / stop Methods with a Fiber — You might reach for a thread to handle this problem, but fibers can get you there with less plumbing and overhead. Per-Test Attribution and Production Coverage — The code coverage tool can now attribute coverage to individual tests, rerun only affected tests on save, cover views (ERB/Haml/Slim), and monitor coverage on production traffic to find code that's not getting used. No Overage Invoices — Errors, traces, Sidekiq, hosts and logs in one gem.
#816 — September 10, 2026 Read on the Web Together with Ruby Weekly RubyKaigi's Talks Are Finally Online RubyKaigi, the conference where Ruby's core team gathers each year, took place in Japan this April, but the talks have just made it onto YouTube with 68 videos in this playlist. Porting Doom – Chris Hasiński on his Ruby DOOM port. Sign up for free and stop worrying about your job queues.
Originally appeared on Rails at Scale . What is Rubydex linter Rubydex is a static analysis toolkit for Ruby. My teammate Vini introduced it in more detail in One engine, many tools — Introducing Rubydex . Rubydex linter is Rubydex’s built-in linter for writing project-specific structural rules that use Rubydex’s under
A repo-aware prompt for Codex, Claude Code, Cursor, and similar tools that audits an existing Rails application for conflicting architectural precedent, missing decisions, structural risks, and agent context gaps.
Originally appeared on The Rails Tech Debt Blog . ERB does not know that it is generating HTML. It finds the <% %> tags, evaluates the Ruby inside them, and concatenates everything else as plain text. Whether the result is valid markup has never been its problem. Herb changes that. On August 25, 2026, the Ruby on Rails
Originally appeared on Shopify Engineering . We built Helix to help LLMs rebuild the Shopify app in Swift and Kotlin, using small checkpoints and strict quality gates to keep the code shippable.
Originally appeared on The Rails Tech Debt Blog . You get a site audit report and it looks manageable. A few dozen findings, most of them small: a page with barely any text on it, a link whose text is just “here”, a page whose title tag is a copy of its H1, a hero image heavy enough to hurt the largest contentful paint
Since 2026 every Shopify storefront answers an agent-commerce endpoint at POST /api/ucp/mcp , advertised at GET /.well-known/ucp . Merchants did not turn it on and it is not in their admin. It speaks the Universal Commerce Protocol over JSON-RPC, and the tool that matters is search_catalog : an AI shopping agent asks a
Loading more related stories...
Open the app view to save this story, compare related coverage, and continue from the same source.
