<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Germán Giménez Silva on Medium]]></title>
        <description><![CDATA[Stories by Germán Giménez Silva on Medium]]></description>
        <link>https://medium.com/@german.gimenez.silva?source=rss-f0e8d8a44f69------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uzRWC9kupehIxp4tOjuJoQ.png</url>
            <title>Stories by Germán Giménez Silva on Medium</title>
            <link>https://medium.com/@german.gimenez.silva?source=rss-f0e8d8a44f69------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:58:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@german.gimenez.silva/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Safely and Efficiently Transform Payloads in Ruby and Ruby on Rails Workflows]]></title>
            <link>https://medium.com/@german.gimenez.silva/how-to-safely-and-efficiently-transform-payloads-in-ruby-and-ruby-on-rails-workflows-2fe82c01bc69?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fe82c01bc69</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[payload]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Fri, 03 Jul 2026 01:57:41 GMT</pubDate>
            <atom:updated>2026-07-03T02:06:56.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LaXMv7x7FsL-VOO7.png" /></figure><p>July 2, 2026</p><p>Modern applications rarely consume external data exactly as it arrives. Whether you’re integrating with payment gateways, CRMs, ERPs, or third-party APIs, incoming payloads almost always need to be normalized, enriched, or reshaped before they can be processed.</p><p>A common workflow looks like this:</p><p>Keeping this transformation layer isolated makes applications easier to maintain, test, and extend as new integrations are added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ejRn4Ksa3ASU1ekh.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JIqVgQCuwPh8a1Kh.png" /></figure><h3>The Transformation Layer</h3><p>Instead of scattering mapping logic across controllers, services, or models, encapsulate it behind a dedicated transformer.</p><p>Usage is straightforward:</p><p>This approach is simple, testable, and works well for most Rails applications.</p><h3>Strategy Pattern for Multiple Integrations</h3><p>When every provider sends a different payload, each integration can have its own transformer.</p><p>Example:</p><p>Adding a new integration becomes a matter of creating a new transformer instead of modifying existing code.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/07/02/how-to-safely-and-efficiently-transform-payloads-in-ruby-and-ruby-on-rails-workflows/">How to Safely and Efficiently Transform Payloads in Ruby and Ruby on Rails Workflows</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NH-8jZP_tHPvmUMh.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/07/02/how-to-safely-and-efficiently-transform-payloads-in-ruby-and-ruby-on-rails-workflows/"><em>http://rubystacknews.com</em></a><em> on July 3, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fe82c01bc69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby 4.0 Is Here. Why Is AI Still Writing Ruby 3.0?]]></title>
            <link>https://medium.com/@german.gimenez.silva/ruby-4-0-is-here-why-is-ai-still-writing-ruby-3-0-d6db5ae1f0e7?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6db5ae1f0e7</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 02:33:56 GMT</pubDate>
            <atom:updated>2026-06-18T02:45:51.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4yhVUGvxZEMBVx6Z.png" /></figure><p>June 17, 2026</p><p>Artificial intelligence has become an indispensable tool for Ruby developers.</p><p>We ask AI assistants to write methods, refactor services, generate RSpec tests, explain stack traces, and even architect new features. For many developers, AI is no longer an experiment-it’s part of the daily workflow.</p><p>That’s exactly why we should expect more from it.</p><p>If I’m writing a Ruby 4.0 application, I don’t want my AI assistant producing Ruby that looks like it came from 2021.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LLxHZl-LuuoDohb4.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wVPIdyGRnDnfCzsp.png" /></figure><h3>Valid Ruby Isn’t Enough</h3><p>One of the most common arguments is that AI-generated code is “still correct.”</p><p>Technically, that’s true.</p><p>But correctness isn’t the only measure of quality.</p><p>Imagine asking for Rails 8 code and receiving Rails 6 patterns. The application would probably still work, but you wouldn’t consider that a good answer.</p><p>The same applies to Ruby.</p><p>When I ask an AI to generate Ruby code, I expect it to use the idioms of the current language-not simply produce syntax that happens to compile.</p><h3>The Evidence Is Everywhere</h3><p>Take Ruby’s hash value omission syntax.</p><p>Instead of writing:</p><p>Modern Ruby allows:</p><p>Yet most AI assistants still default to the longer version.</p><p>The same happens with hashes:</p><p>Instead, AI frequently generates:</p><p>Another example is Ruby’s anonymous block parameter.</p><p>Modern Ruby lets us write:</p><p>Yet AI almost always produces:</p><p>None of these examples are wrong.</p><p>They’re simply not modern Ruby.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/17/ruby-4-0-is-here-why-is-ai-still-writing-ruby-3-0/">Ruby 4.0 Is Here. Why Is AI Still Writing Ruby 3.0?</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2mQwYaeAxPp6UgaK.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/17/ruby-4-0-is-here-why-is-ai-still-writing-ruby-3-0/"><em>http://rubystacknews.com</em></a><em> on June 18, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6db5ae1f0e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Week in Rails: Better Guides, Better Framework]]></title>
            <link>https://medium.com/@german.gimenez.silva/this-week-in-rails-better-guides-better-framework-a0453390fd47?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0453390fd47</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 01:32:48 GMT</pubDate>
            <atom:updated>2026-06-11T14:32:13.792Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LNujq5a6SER1BVN8.png" /></figure><p>June 10, 2026</p><p>The Rails team had another busy week, shipping documentation improvements, infrastructure updates, and a collection of bug fixes across the framework.</p><p>Here are some of the highlights.</p><h3>📚 The Active Job Guide Gets a Major Refresh</h3><p>The revamped Active Job Basics guide is now live.</p><p>It covers everything from Solid Queue and background jobs to testing, debugging, and bulk enqueueing. Whether you’re new to background processing or looking to modernize an existing application, the updated guide is worth revisiting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*de10wABkoHnzSWVe.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3HmVcRiyEflzbtnW.png" /></figure><h3>🔌 Action Cable Moves Toward redis-client</h3><p>Action Cable’s Redis adapter is being reimplemented using redis-client.</p><p>The change reduces Rails’ dependency footprint while simplifying subscription handling behind the scenes. Most applications won’t need to make any changes, but it’s another example of Rails gradually streamlining its internals.</p><h3>🖼️ Active Storage Updated for ImageProcessing 2.0</h3><p>Applications using Active Storage should be aware of upcoming ImageProcessing 2.0 requirements.</p><p>Developers now need to explicitly include ruby-vips and/or mini_magick, and newer versions of libvips block several untrusted image formats by default.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/10/this-week-in-rails-better-guides-better-framework/">This Week in Rails: Better Guides, Better Framework</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hwZEKZCkmBF7Ub-d.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/10/this-week-in-rails-better-guides-better-framework/"><em>http://rubystacknews.com</em></a><em> on June 11, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0453390fd47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hidden DSL Inside Every Rails Model]]></title>
            <link>https://medium.com/@german.gimenez.silva/the-hidden-dsl-inside-every-rails-model-7fe7c9c79782?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fe7c9c79782</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[activerecord]]></category>
            <category><![CDATA[model]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Wed, 10 Jun 2026 03:03:29 GMT</pubDate>
            <atom:updated>2026-06-10T15:54:32.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oYEorCEkMtwULenn.png" /></figure><p>June 10, 2026</p><p>Most Rails developers use belongs_to, has_many, scope, and validates every day.</p><p>We type them almost without thinking.</p><p>But here’s something interesting:</p><p>None of those are Ruby keywords.</p><p>They’re methods.</p><p>In fact, a Rails model is less like a traditional Ruby class and more like a Domain Specific Language (DSL) built on top of Ruby.</p><p>Once you see it, it’s hard to unsee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SBKj38IHEm4Tt81_.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pBTmEhPPnUyNpMSM.png" /></figure><h3>The Empty Model</h3><p>A Rails model starts life as a completely ordinary Ruby class.</p><p>At first glance, there’s nothing special here.</p><p>User inherits from ApplicationRecord, which inherits from ActiveRecord::Base.</p><p>That’s where the magic begins.</p><p>By inheriting from Active Record, the class gains hundreds of methods that allow us to describe data, relationships, validations, callbacks, and behavior using a concise DSL.</p><h3>Associations</h3><p>Consider this:</p><p>When Rails reads these lines, it isn’t creating relationships in the database.</p><p>It’s executing methods.</p><p>Those methods generate additional behavior behind the scenes.</p><p>After declaring belongs_to :company, Rails creates methods such as:</p><p>A single line of DSL expands into a collection of Ruby methods.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/10/the-hidden-dsl-inside-every-rails-model/">The Hidden DSL Inside Every Rails Model</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6bNRbf4SMb4SvCzG.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/10/the-hidden-dsl-inside-every-rails-model/"><em>http://rubystacknews.com</em></a><em> on June 10, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fe7c9c79782" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Shared Echo: Understanding Ruby on Rails’ Request-Response Cycle]]></title>
            <link>https://medium.com/@german.gimenez.silva/the-shared-echo-understanding-ruby-on-rails-request-response-cycle-dfe5e785c03e?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfe5e785c03e</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[cors]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 01:50:42 GMT</pubDate>
            <atom:updated>2026-06-09T02:02:23.294Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2ymtizcwtaXC3geU.png" /></figure><p>June 8, 2026</p><p>As developers, we often chase the big topics.</p><p>Distributed systems.</p><p>Microservices.</p><p>Event-driven architectures.</p><p>AI.</p><p>Scalability.</p><p>Performance.</p><p>The industry constantly presents us with bigger mountains to climb.</p><p>In that pursuit, we sometimes walk past the things we use every single day.</p><p>The familiar.</p><p>The routine.</p><p>The pieces that quietly do their job without asking for attention.</p><p>One of those pieces is the Ruby on Rails request-response cycle.</p><p>Every page we render.</p><p>Every API endpoint we expose.</p><p>Every button a user clicks.</p><p>Every request follows the same journey.</p><p>Most of us know the destination.</p><p>Fewer of us stop to appreciate the path.</p><p>Today, I’d like to explore that path through a different lens.</p><p>Not as a pipeline.</p><p>Not as a stack.</p><p>But as a shared echo.</p><h3>Read Complete article</h3><p><a href="https://rubystacknews.com/2026/06/08/the-shared-echo-understanding-ruby-on-rails-request-response-cycle/">The Shared Echo: Understanding Ruby on Rails&#39; Request-Response Cycle</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vAfKdJE6DfS3-iI2.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/08/the-shared-echo-understanding-ruby-on-rails-request-response-cycle/"><em>http://rubystacknews.com</em></a><em> on June 9, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe5e785c03e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby’s Ancestor Chain: Why prepend Cuts the Line]]></title>
            <link>https://medium.com/@german.gimenez.silva/rubys-ancestor-chain-why-prepend-cuts-the-line-8f897324df48?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f897324df48</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 01:57:39 GMT</pubDate>
            <atom:updated>2026-06-08T02:10:08.850Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E56O8PkpxC_YVT2n.png" /></figure><p>June 7, 2026</p><p>When Ruby receives a method call, it follows a well-defined search path to determine where that method is implemented. Most developers learn inheritance early, but fewer take the time to understand the complete method lookup path, also known as the ancestor chain.</p><p>Understanding this mechanism can make debugging easier, clarify how Rails works under the hood, and explain why prepend behaves differently from include.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GKlhwuJXb_eKxnZt.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ypZP-BR-8HF8e6a6.png" /></figure><p>A Stack of Dishes</p><p>Imagine a pile of dishes waiting to be washed.</p><p>The last dish placed on the pile is the first one to be taken off. This is the classic LIFO (Last In, First Out) principle.</p><p>Ruby’s ancestor chain behaves similarly.</p><p>When modules are included in a class, Ruby places them into the lookup path. The most recently included module gets higher priority than modules included earlier.</p><p>Consider the following example:</p><p>Output:</p><p>Notice that Dry appears before Wash.</p><p>Although Wash was included first, Dry was included later and receives priority during method lookup.</p><p>If we execute:</p><p>Ruby will find process in Dry before reaching Wash.</p><p>The last module added gets searched first, much like the last dish added to a stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*r_FMbTeG31vatEbD.png" /></figure><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/07/rubys-ancestor-chain-why-prepend-cuts-the-line/">Ruby&#39;s Ancestor Chain: Why prepend Cuts the Line</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Uge8jmnMeObMl1XX.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/07/rubys-ancestor-chain-why-prepend-cuts-the-line/"><em>http://rubystacknews.com</em></a><em> on June 8, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f897324df48" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RubyGems 4.0.13 and Bundler 4.0.13 Released with New Supply-Chain Security Protections]]></title>
            <link>https://medium.com/@german.gimenez.silva/rubygems-4-0-13-and-bundler-4-0-13-released-with-new-supply-chain-security-protections-ca77a60f7e1d?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca77a60f7e1d</guid>
            <category><![CDATA[rubygems]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[bundler]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 02:49:43 GMT</pubDate>
            <atom:updated>2026-06-08T02:35:20.405Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p_G0TA-ZbLJi38J3.png" /></figure><p>June 3, 2026</p><p>The RubyGems team has released RubyGems 4.0.13 and Bundler 4.0.13, bringing a combination of security improvements, bug fixes, and quality-of-life enhancements for Ruby developers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ErKCcFlrdIBtMMzV.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2HDFK6EVuJJhWHWQ.png" /></figure><p>While this is a relatively small release, it includes a notable new security feature designed to help protect developers from supply-chain attacks.</p><h3>Cooldown Protection for Newly Published Gems</h3><p>The headline feature of Bundler 4.0.13 is the introduction of a cooldown mechanism for newly published gems.</p><p>The new feature delays the installation of freshly published gem versions, providing an additional layer of defense against malicious package releases and compromised maintainer accounts. Similar protections have been discussed and implemented across several package ecosystems as software supply-chain attacks continue to grow in frequency and sophistication.</p><p>For teams that prioritize stability and security, this feature offers a practical safeguard against accidentally installing a malicious version immediately after publication.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/03/rubygems-4-0-13-and-bundler-4-0-13-released-with-new-supply-chain-security-protections/">RubyGems 4.0.13 and Bundler 4.0.13 Released with New Supply-Chain Security Protections</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8iTUluXmWTACezSM.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/03/rubygems-4-0-13-and-bundler-4-0-13-released-with-new-supply-chain-security-protections/"><em>http://rubystacknews.com</em></a><em> on June 4, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca77a60f7e1d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning a Generic LLM Into a Ruby-LibGD Expert (One Correction at a Time)]]></title>
            <link>https://medium.com/@german.gimenez.silva/turning-a-generic-llm-into-a-ruby-libgd-expert-one-correction-at-a-time-6e2003ef1391?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e2003ef1391</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ruby-libgd]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 02:49:22 GMT</pubDate>
            <atom:updated>2026-06-08T02:31:40.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IunSPO-zfGbPPcq8.png" /></figure><p>June 2, 2026</p><p><em>What a day of conversations taught me about context, memory, and the limits of local AI models.</em></p><p>A few days ago, I started what seemed like a simple experiment.</p><p>I wanted a local LLM to help me work on a Ruby gem I’ve been developing: <strong>Ruby-LibGD</strong>, a Ruby binding for the GD Graphics Library.</p><p>The goal wasn’t complicated. I wanted the model to help me create examples, improve documentation, generate tutorials, and eventually contribute code.</p><p>What followed became an accidental study of how modern LLMs learn-or more accurately, how they <em>appear</em> to learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*euJF3gGpyt2zhRTV.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gblH1DKT6jDEJf3j.png" /></figure><h3>The First Problem: The Model Didn’t Know My Library</h3><p>The first requests seemed straightforward:</p><blockquote><em>Could you graph a 2D function using Ruby-LibGD?</em></blockquote><p>The model answered confidently.</p><p>Too confidently.</p><p>It produced code using methods such as:</p><p>The problem?</p><p>Neither method exists in Ruby-LibGD.</p><p>The model wasn’t lying. It was doing what LLMs do best: predicting what <em>looks</em> plausible.</p><p>Its training data likely contained examples from:</p><ul><li>PHP’s GD library</li><li>Older GD bindings</li><li>Generic graphics libraries</li><li>Similar APIs from other languages</li></ul><p>The result was believable code that would never run.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/02/turning-a-generic-llm-into-a-ruby-libgd-expert-one-correction-at-a-time/">Turning a Generic LLM Into a Ruby-LibGD Expert (One Correction at a Time)</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q2csGDAIngmNfVw_.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/02/turning-a-generic-llm-into-a-ruby-libgd-expert-one-correction-at-a-time/"><em>http://rubystacknews.com</em></a><em> on June 3, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e2003ef1391" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Original Sin, the Scorpion, and Local AI]]></title>
            <link>https://medium.com/@german.gimenez.silva/the-original-sin-the-scorpion-and-local-ai-98600c46fb6c?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/98600c46fb6c</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[methaphore]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 01:57:53 GMT</pubDate>
            <atom:updated>2026-06-08T02:28:52.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rx354n7FPH512YSf" /></figure><p>June 1, 2026</p><p>For the last few weeks, I have been experimenting with local AI models to help me develop and maintain Ruby projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LKLzR9J0Ym-d6vs9.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jv1ezTOqt93R9VHV.png" /></figure><p>The goal sounded simple enough.</p><p>I wanted an assistant capable of understanding Ruby, Ruby on Rails, Ruby-LibGD, Ruby-GIS, and a collection of libraries and projects that I have worked on over the years.</p><p>Like many developers exploring local AI, I started downloading models, testing embeddings, building RAG pipelines, and indexing documentation.</p><p>At first, everything looked promising.</p><p>The models could answer basic questions.</p><p>They could generate small scripts.</p><p>They could explain simple algorithms.</p><p>But as soon as I moved beyond toy examples and into real-world codebases, the limitations became impossible to ignore.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/01/the-original-sin-the-scorpion-and-local-ai/">The Original Sin, the Scorpion, and Local AI</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BtP49U3cgn2EmebW.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/01/the-original-sin-the-scorpion-and-local-ai/"><em>http://rubystacknews.com</em></a><em> on June 2, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98600c46fb6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turning Years of Ruby Knowledge Into a Local Coding Assistant]]></title>
            <link>https://medium.com/@german.gimenez.silva/turning-years-of-ruby-knowledge-into-a-local-coding-assistant-24b72f85e71e?source=rss-f0e8d8a44f69------2</link>
            <guid isPermaLink="false">https://medium.com/p/24b72f85e71e</guid>
            <category><![CDATA[ollama]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[chromadb]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Germán Giménez Silva]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 03:09:11 GMT</pubDate>
            <atom:updated>2026-06-08T02:26:57.257Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8RTP393z-4_M8vBw.png" /></figure><p>June 1, 2026</p><h3>Introduction</h3><p>Over the years, most Ruby developers accumulate a vast amount of knowledge.</p><p>Not just source code, but articles, documentation, experiments, bug fixes, pull requests, design decisions, and lessons learned from maintaining production systems.</p><p>The problem is that this knowledge often remains scattered across repositories, blogs, notes, and forgotten directories. Even when the information exists, finding the right piece of knowledge at the right time can be surprisingly difficult.</p><p>Recent advances in local AI models have created an interesting opportunity: what if we could turn years of accumulated Ruby expertise into a coding assistant that understands our tools, libraries, and development practices?</p><p>This article explores that idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f4hwFjxnhdVNsN1a.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l5ssdQxcnbxylyrd.png" /></figure><h3>The Knowledge Gap</h3><p>Modern language models generally understand Ruby reasonably well. They can explain blocks, classes, modules, metaprogramming, and common Rails patterns.</p><p>However, they know very little about:</p><ul><li>Custom gems</li><li>Internal company libraries</li><li>Specialized Ruby ecosystems</li><li>Private codebases</li><li>Years of project-specific experience</li></ul><p>For example, asking a model how to expose a GIS structure through a Ruby C extension may produce a generic answer. The model understands Ruby and C, but it does not understand the conventions, architecture, and design decisions that evolved within a specific project.</p><p>The missing piece is context.</p><h3>👉 Read the full article.</h3><p><a href="https://rubystacknews.com/2026/06/01/turning-years-of-ruby-knowledge-into-a-local-coding-assistant/">Turning Years of Ruby Knowledge Into a Local Coding Assistant</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qudDhZWnurgzBaH9.png" /></figure><p><em>Originally published at </em><a href="https://rubystacknews.com/2026/06/01/turning-years-of-ruby-knowledge-into-a-local-coding-assistant/"><em>http://rubystacknews.com</em></a><em> on June 1, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24b72f85e71e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>