<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:thoughtbot="https://thoughtbot.com/feeds/">
  <title>Giant Robots Smashing Into Other Giant Robots</title>
  <subtitle>Written by thoughtbot, your expert partner for design and development.
</subtitle>
  <id>https://robots.thoughtbot.com/</id>
  <link href="https://thoughtbot.com/blog"/>
  <link href="https://feed.thoughtbot.com" rel="self"/>
  <updated>2026-11-19T00:00:00+00:00</updated>
  <author>
    <name>thoughtbot</name>
  </author>
<entry>
  <title>Ruby security update: Critical fixes in versions 4.0.10, 3.4.13, and 3.3.14</title>
  <link rel="alternate" href="https://thoughtbot.com/blog/ruby-security-update-critical-fixes-in-versions-4-0-10-3-4-13-and-3-3-14"/>
  <author>
    <name>Lindsey Christensen</name>
  </author>
  <id>https://thoughtbot.com/blog/ruby-security-update-critical-fixes-in-versions-4-0-10-3-4-13-and-3-3-14</id>
  <published>2026-11-19T00:00:00+00:00</published>
  <updated>2026-11-19T19:48:25Z</updated>
  <content type="html">&lt;p&gt;On November 18, 2026, the Ruby team released security updates addressing seven vulnerabilities in Ruby’s regular expression engine and string case conversion.&lt;/p&gt;

&lt;p&gt;Several of these vulnerabilities could allow remote code execution under certain conditions, with proof-of-concept exploits already demonstrated. Other vulnerabilities could lead to memory disclosure or application crashes. The Ruby team strongly recommends upgrading.&lt;/p&gt;
&lt;h2 id="what-you-need-to-do"&gt;
  
    What you need to do
  
&lt;/h2&gt;

&lt;p&gt;If you’re running a Ruby application, check your current version and upgrade to the appropriate security release:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ruby 4.0:&lt;/strong&gt; Upgrade to 4.0.10&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ruby 3.4:&lt;/strong&gt; Upgrade to 3.4.13&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ruby 3.3:&lt;/strong&gt; Upgrade to 3.3.14&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ruby 3.2 and earlier have reached end of life and will not receive these security fixes. If your application is running an unsupported version, it’s important to plan an upgrade to a supported release.&lt;/p&gt;

&lt;p&gt;Review the &lt;a href="https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/"&gt;official Ruby security advisory&lt;/a&gt; for full technical details.&lt;/p&gt;
&lt;h2 id="stay-ahead-of-security-risks"&gt;
  
    Stay ahead of security risks
  
&lt;/h2&gt;

&lt;p&gt;This release is a reminder that keeping software dependencies up to date is an important part of maintaining secure, reliable applications.&lt;/p&gt;

&lt;p&gt;As we explained in &lt;a href="https://thoughtbot.com/blog/your-legacy-software-is-a-ticking-bomb#stay-ahead-of-the-clock"&gt;Your legacy software is a ticking bomb&lt;/a&gt;, regular maintenance makes upgrades easier and helps prevent security vulnerabilities from accumulating.&lt;/p&gt;

&lt;p&gt;Not sure whether your projects are running unsupported versions? Check out the &lt;a href="https://thoughtbot.com/blog/your-legacy-software-is-a-ticking-bomb#end-of-life-is-here"&gt;End of Life tool&lt;/a&gt; to scan your repositories and identify outdated Ruby versions.&lt;/p&gt;

&lt;p&gt;Don’t wait for a security incident to prioritize maintenance. Review your Ruby versions and schedule the appropriate updates. As always, &lt;a href="https://thoughtbot.com/services/ruby-on-rails"&gt;we’re here to help if you need it.&lt;/a&gt;&lt;/p&gt;

&lt;aside class="related-articles"&gt;&lt;h2&gt;If you enjoyed this post, you might also like:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://thoughtbot.com/blog/rails-2-3-2-upgrade-gotchas"&gt;Rails 2.3.2 upgrade gotchas&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thoughtbot.com/blog/the-journey-to-ruby-1-9"&gt;The Journey to Ruby 1.9 &lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thoughtbot.com/blog/clearance-0-16-3-fixes-a-password-reset-vulnerability"&gt;Clearance 0.16.3 fixes a password reset vulnerability&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/aside&gt;
</content>
  <summary>Ruby security updates address seven vulnerabilities. Learn which versions are affected, what to upgrade, and how to keep your applications secure.</summary>
  <thoughtbot:auto_social_share>true</thoughtbot:auto_social_share>
</entry>
<entry>
  <title>Friction worth protecting when shaping products</title>
  <link rel="alternate" href="https://thoughtbot.com/blog/friction-worth-protecting-when-shaping-products"/>
  <author>
    <name>Andrew Spencer</name>
  </author>
  <id>https://thoughtbot.com/blog/friction-worth-protecting-when-shaping-products</id>
  <published>2026-11-19T00:00:00+00:00</published>
  <updated>2026-11-18T16:01:14Z</updated>
  <content type="html">&lt;p&gt;Today, with the rise of LLMs that can generate a product brief or full prototypes in minutes, friction between a product concept and a polished deliverable is getting smaller and smaller. The tools and processes for product discovery and shaping have changed rapidly. Founders and product teams are shaping ideas with AI and can move quickly but this loss of friction can lead to shipping the wrong thing if we’re not careful.&lt;/p&gt;
&lt;h2 id="categorizing-friction"&gt;
  
    Categorizing friction
  
&lt;/h2&gt;

&lt;p&gt;The debate around the question “is the way AI removes friction a good thing” is certainly &lt;a href="https://www.nature.com/articles/s44271-026-00402-1"&gt;not&lt;/a&gt; &lt;a href="https://www.foundingfuel.com/article/why-we-need-good-friction-in-the-age-of-ai"&gt;new&lt;/a&gt; but I recently heard Fabio Cortez speak at &lt;a href="https://webflow.com/webflowconf/session/from-sketch-to-shipped-how-design-intent-travels-through-agents"&gt;Webflow Conf&lt;/a&gt; and this quote stuck with me:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;there are two kinds of friction, one we want to automate, the friction between me and my intent, the repetition, translation, reconstruction happening between stakeholders, we should automate that. But the friction between us and the problem we’re trying to solve, we should not automate, we should protect it always, that’s where the magic happens, the ambiguity, the critique, the exploration, that’s the friction to protect.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Fabio does a great job articulating two categories of friction:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Intent friction&lt;/strong&gt; – not ideal&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Problem friction&lt;/strong&gt; – important&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Intent friction&lt;/strong&gt; is what slows down your ability to effectively articulate an idea or build a clearly defined feature. It assumes the direction is validated and focused. This can look like visualizing a concept you’re discussing as a team, designing a common UI pattern, writing code for a component you’ve built before, or documenting existing patterns.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Problem friction&lt;/strong&gt; arises when the solution isn’t clear. It looks like slowing down to ask why, discussing different opinions as a team, critiquing your design work, or exploring a wide variety of ideas. It’s ambiguity and constraints, critique and conflicting ideas, messy exploration and sparking new ideas. The human side of shaping and building products.&lt;/p&gt;
&lt;h2 id="friction-uncovers-assumptions"&gt;
  
    Friction uncovers assumptions
  
&lt;/h2&gt;

&lt;p&gt;Problem friction is useful because it allows us to uncover assumptions that add risk to the product. It’s an opportunity to ask bigger questions. To slow down and ensure what you’re planning to build is grounded and the whole concept doesn’t hinge on an ambiguous, untested theory.&lt;/p&gt;
&lt;h3 id="a-note-on-llms"&gt;
  
    A note on LLMs
  
&lt;/h3&gt;

&lt;p&gt;LLMs hate ambiguity so they fill in the gaps with assumptions. Attempting to minimize friction by using LLMs can result in products that don’t actually align with user needs or serve the long term goals of the business. LLMs look for patterns and their output tends to &lt;a href="https://arxiv.org/abs/2603.13036"&gt;look the same&lt;/a&gt;, meaning the more you rely on LLMs to shape or build your product, the more it will look like every other app and gradually lose its soul and distinct purpose.&lt;/p&gt;

&lt;p&gt;Sure LLMs can be a helpful sounding board for your ideas and their output can be improved with skills but it’s still an imperfect solution that often gives &lt;a href="https://www.science.org/doi/10.1126/science.aec8352"&gt;sycophantic&lt;/a&gt; answers, meaning it will tell you what you want to hear. This is partly why we built &lt;a href="https://readysetgo.dev/"&gt;ReadySetGo&lt;/a&gt;, to help shape ideas and surface hidden assumptions that need testing before you build anything.&lt;/p&gt;
&lt;h2 id="testing-validates-assumptions"&gt;
  
    Testing validates assumptions
  
&lt;/h2&gt;

&lt;p&gt;If problem friction finds assumptions, how do you test and validate these assumptions? Nothing beats talking to users. A team or LLM can hypothesize about how to move forward, but the best way to build true confidence is to get in front of the real people who will use the product you’re envisioning. Listen to users articulate their problems before offering a solution, often this will reveal far more interesting information than showing them a solution that already has your biased perspective baked in.&lt;/p&gt;

&lt;p&gt;What we hear from people during user interviews almost always challenges some of our pre-conceived assumptions. This causes us to change everything from the features we prioritize building to small details like the text in a button. Sometimes it causes us to re-think the entire approach. On the flip side, it also gives us confidence when we see users respond well to our ideas.&lt;/p&gt;
&lt;h2 id="sprints-as-a-framework-for-problem-friction"&gt;
  
    Sprints as a framework for problem friction
  
&lt;/h2&gt;

&lt;p&gt;At thoughtbot we use &lt;a href="https://thoughtbot.com/services/shaping-sprint"&gt;shaping sprints&lt;/a&gt; to clarify what we plan to build. Shaping sprints allow us to ask questions that probe at the product’s core idea. While this can sometimes feel uncomfortable, this kind of problem friction is critical for uncovering assumptions.&lt;/p&gt;

&lt;p&gt;A quick story. On a recent sprint for a new project, the team came in confident with a product plan and prototype built with an LLM. On the surface it seemed sound, and it looked pretty. The prototype worked and proved the idea was technically possible, but it was hiding an array of assumptions about how people would use the product and how scaling features would change the experience. Thankfully the shaping sprint caught these assumptions early and we were able to quickly pivot and have confidence that our new direction would actually resonate with users.&lt;/p&gt;
&lt;h2 id="an-important-question"&gt;
  
    An important question
  
&lt;/h2&gt;

&lt;p&gt;Not every decision benefits from problem friction. When the solution is clear and the team knows why, either from data or because the problem has been solved before by others, any friction between your idea and a working product is &lt;em&gt;intent&lt;/em&gt; friction and is safe to minimize through using LLMs.&lt;/p&gt;

&lt;p&gt;How do you distinguish &lt;em&gt;intent&lt;/em&gt; friction from &lt;em&gt;problem&lt;/em&gt; friction? Ask yourself:&lt;/p&gt;

&lt;p&gt;Can you fully describe the result you want, explain &lt;em&gt;why&lt;/em&gt; it’s shaped that way, and point to evidence that validates the assumptions behind it?&lt;/p&gt;

&lt;p&gt;If there’s any hesitation or ambiguity, you’re looking at problem friction. Ignoring this friction risks baking assumptions into your product, which could result in product/market mismatch, failed customer acquisition, or extra development time and expense.&lt;/p&gt;

&lt;aside class="related-articles"&gt;&lt;h2&gt;If you enjoyed this post, you might also like:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://thoughtbot.com/blog/how-to-use-chatgpt-to-find-custom-software-consultants"&gt;How to Use ChatGPT to Find Custom Software Consultants&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thoughtbot.com/blog/from-idea-to-impact-the-role-of-rapid-prototyping-in-agetech"&gt;From idea to impact: The role of rapid prototyping in AgeTech&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thoughtbot.com/blog/theme-based-iterations"&gt;Theme-Based Iterations&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/aside&gt;
</content>
  <summary>LLMs reduce friction in shaping and building products but a certain type of friction is critical for uncovering risky assumptions.</summary>
  <thoughtbot:auto_social_share>true</thoughtbot:auto_social_share>
</entry>
</feed>
