<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on The Traveling Engineer</title><link>http://traveling.engineer/</link><description>Recent content in Home on The Traveling Engineer</description><generator>Hugo</generator><language>en-us</language><copyright>Samuel Giddins</copyright><lastBuildDate>Tue, 15 Apr 2025 10:52:43 +0900</lastBuildDate><atom:link href="http://traveling.engineer/index.xml" rel="self" type="application/rss+xml"/><item><title>Ruby Release Reproducibility</title><link>http://traveling.engineer/posts/ruby-release-reproducibility/</link><pubDate>Tue, 15 Apr 2025 10:52:43 +0900</pubDate><guid>http://traveling.engineer/posts/ruby-release-reproducibility/</guid><description>&lt;p>I wanted to outline a few findings around the reproducibility of the official Ruby releases.&lt;/p></description></item><item><title>Goals for Binary Gems ("Wheels")</title><link>http://traveling.engineer/posts/goals-for-binary-gems/</link><pubDate>Mon, 24 Feb 2025 04:30:00 +0100</pubDate><guid>http://traveling.engineer/posts/goals-for-binary-gems/</guid><description>&lt;p>We want to encourage gem authors to ship precompiled binaries of their gems whenever possible (instead of the gem building an extension at install time).
This is better for security &amp;ndash; no code running at install time, and more ergonomic for users &amp;ndash; no need to install build tools, deal with build errors, waiting for slow compilation.&lt;/p>
&lt;p>Problem statement: Dealing with gems that have different implementations and requirements across different OSes, CPU architectures, libc Ruby Engines, Ruby versions, (and ruby engine versions) is challenging for both gem authors and consumers.&lt;/p></description></item><item><title>January 2025 Residency Update</title><link>http://traveling.engineer/posts/2025-01-update/</link><pubDate>Thu, 30 Jan 2025 22:30:00 -0800</pubDate><guid>http://traveling.engineer/posts/2025-01-update/</guid><description>&lt;p>A quick update on what&amp;rsquo;s been happening in the past month. Abbreviated, since there was both vacation and a sick week somehow squeezed in there.&lt;/p></description></item><item><title>2024 in Review</title><link>http://traveling.engineer/posts/2024-in-review/</link><pubDate>Fri, 24 Jan 2025 13:17:12 -0800</pubDate><guid>http://traveling.engineer/posts/2024-in-review/</guid><description>&lt;p>2024 was an eventful year, both personally &amp;amp; as the Ruby Central Security Engineer in Residence.&lt;/p>
&lt;p>In my first year working full-time on the Ruby packaging ecosystem I shipped some bugs, a few big projects, and built relationships with some incredible folks working in the software supply chain space.&lt;/p>
&lt;p>Oh, I also got married. Can&amp;rsquo;t forget that.&lt;/p>
&lt;p>Read on for some of the highlights, keeping in mind that there&amp;rsquo;s always ongoing maintenance work on Bundler, RubyGems, and RubyGems.org.&lt;/p></description></item></channel></rss>