What if AI could make your work more creative instead of more crowded? We sit down with Scott Werner to unpack a practical path for Ruby developers who want the leverage of AI without sacrificing taste, clarity, or joy. From agentic coding with Claude Code to context-rich tools like Tidewave, we walk through how better inputs—logs, DOM access, database state—turn generic suggestions into usable plans that reduce cognitive load and speed up real problem solving.

Scott shares the origin story of Artificial Ruby, a New York meetup that started as a casual happy hour and became a monthly mini conference. That community energy matters: many devs began their careers remotely and missed the spark of live conversations. By focusing on play and curiosity, the group channels the early Ruby vibe—ship small experiments, trade sharp feedback, and rediscover the fun of making software together. That ethos powers Scott’s projects: Monkey’s Paw, a prompt-based web framework that leans into expressive generation, and Latent Library, a hallucinatory book explorer that asks what new interfaces AI enables.

We also tackle the “slop generator” problem and how to curb it. Different models have different tendencies, so route tasks where they fit: broad ideation to one, surgical changes to another. Constrain edits, ask for reasoning before code, and hand the model real context so it can propose focused steps. The same philosophy informs testing with computer-use models: if an agent can’t find your logout or complete checkout by looking at the UI, maybe your users struggle too. Rather than replacing developers, these tools elevate the craft—pushing commodity work downward while widening the canvas for design, problem framing, and tasteful implementation.

Want more? Check out ArtificialRuby.ai for upcoming events and videos, explore LatentLibrary.xyz, and find Scott’s essays and tutorials at WorksOnMyMachine.ai. If this conversation helps you rethink your workflow, follow, share with a teammate, and leave a review so more builders can join the experiment.

Send us some love.

Support the show

In this episode of C4, Andrew Mason and Rachael Wright-Munn join Drew to unpack recent controversies surrounding Ruby Central and its alleged takeover of Ruby Gems and Bundler. The trio delves into the timeline of events, conflicting narratives, communication failures, and the underlying security concerns. They address theories and facts, scrutinize the governance of Ruby Central, and discuss the implications for the Ruby community. The episode emphasizes the importance of asking questions and seeking clarity, while advocating for a balanced and constructive approach to resolving the community's issues.

Sources discussed*:

• Ellen's first post on the RubyGems controversy
• A board member's perspective on the RubyGems controversy
• An Update From Ruby Central (Video)
• Investigation (allegedly) reveals Shopify manipulated Ruby Central to force takeover of Bundler and RubyGems
• Strengthening the Stewardship of RubyGems and Bundler
• Martin Emde's post on Bluesky
• Reddit post for "An update from Ruby Central"
• Bundler Policies on GitHub
• Ruby Central "About" page
• Advocacy for Reduced Rails Usage
• Alpha-Omega Project
• Organization & Structure of Open Source Software Development Initiatives - Cyberlaw Clinic
• Ruby Central News Post: Alpha-Omega support
• StepSecurity: npm supply chain compromise
• Socket: npm supply chain attack
• Palo Alto Networks Unit 42: npm supply chain attack

* Some sources include unverified information being presented as fact. Read with caution.

Send us some love.

Support the show

Ruby core team member Aaron Patterson (tenderlove) takes us deep into the cutting edge of Ruby's performance frontier in this technical exploration of how one of the world's most beloved programming languages continues to evolve.

At Shopify, Aaron works on two transformative projects: ZJIT, a method-based JIT compiler that builds on YJIT's success by optimizing register allocation to reduce memory spills, and enhanced Ractor support to enable true CPU parallelism in Ruby applications. He explains the fundamental differences between these approaches - ZJIT makes single CPU utilization more efficient, while Ractors allow Ruby code to run across multiple CPUs simultaneously.

The conversation reveals how real business needs drive language development. Shopify's production workloads unpredictably alternate between CPU-bound and IO-bound tasks, creating resource utilization challenges. Aaron's team aims to build auto-scaling web server infrastructure using Ractors that can dynamically adjust to workload characteristics - potentially revolutionizing how Ruby applications handle variable traffic patterns.

For developers interested in contributing to Rails, Aaron offers practical advice: start reading the source code, understand the architecture, and look for ways to improve it. He shares insights on the challenges of making Rails Ractor-safe, particularly around passing lambdas between Ractors while maintaining memory safety.

The episode concludes with a delightful tangent into Aaron's latest hardware project - building a color temperature sensor for camera calibration that combines his photography hobby with his programming expertise. True to form, even his leisure activities inevitably transform into coding projects.

Whether you're a seasoned Ruby developer or simply curious about language design and performance optimization, Aaron's unique blend of deep technical knowledge and playful enthusiasm makes this an engaging journey through Ruby's exciting future.

Send us some love.

Support the show