<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Avery Rivera</title>
    <description>The latest articles on DEV Community by Avery Rivera (@rivera_71).</description>
    <link>https://dev.to/rivera_71</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210618%2Fc6c0440a-4b09-4750-8873-71a9148ef3d2.jpg</url>
      <title>DEV Community: Avery Rivera</title>
      <link>https://dev.to/rivera_71</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rivera_71"/>
    <language>en</language>
    <item>
      <title>Rails 8: what I actually use from it</title>
      <dc:creator>Avery Rivera</dc:creator>
      <pubDate>Wed, 28 Oct 2026 04:37:11 +0000</pubDate>
      <link>https://dev.to/rivera_71/rails-8-what-i-actually-use-from-it-59gf</link>
      <guid>https://dev.to/rivera_71/rails-8-what-i-actually-use-from-it-59gf</guid>
      <description>&lt;p&gt;I've been on Rails 8 for a few months on a side project. Here's what I actually use day to day, versus what I expected to use.&lt;/p&gt;

&lt;p&gt;Used constantly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Solid Queue for background jobs&lt;/li&gt;
&lt;li&gt;Solid Cache (one less service to run)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;bin/setup&lt;/code&gt; style scripts&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Barely used:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Kamal (great, but I deploy to one box)&lt;/li&gt;
&lt;li&gt;Propshaft (nice, still learning the edges)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My take: the "no extra services" direction is the real win. A side project that runs on one box with a database and a queue in the same database is exactly what I want at 2am.&lt;/p&gt;

&lt;p&gt;I'm still slowly reading SQLite internals. The more I learn about storage, the more I appreciate how much Rails hides.&lt;/p&gt;

</description>
      <category>rails</category>
      <category>ruby</category>
      <category>webdev</category>
    </item>
    <item>
      <title>SQLite is the side-project database I keep coming back to</title>
      <dc:creator>Avery Rivera</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:42:39 +0000</pubDate>
      <link>https://dev.to/rivera_71/sqlite-is-the-side-project-database-i-keep-coming-back-to-25bj</link>
      <guid>https://dev.to/rivera_71/sqlite-is-the-side-project-database-i-keep-coming-back-to-25bj</guid>
      <description>&lt;p&gt;Every side project I start, I ask myself if I need Postgres. The answer is almost always no.&lt;/p&gt;

&lt;p&gt;SQLite gives me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A single file I can back up by copying&lt;/li&gt;
&lt;li&gt;Zero ops&lt;/li&gt;
&lt;li&gt;More than enough performance for a side project&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The caveat is concurrency. Once you have background jobs writing at the same time as requests, you need to think about WAL mode and busy timeouts. That's a 20-minute fix, not a reason to run a database server.&lt;/p&gt;

&lt;p&gt;My current side project is Rails + SQLite, and the whole thing deploys as one container with a mounted volume.&lt;/p&gt;

&lt;p&gt;I'm slowly reading about SQLite internals — the page format is a lot more approachable than I expected.&lt;/p&gt;

</description>
      <category>sqlite</category>
      <category>rails</category>
      <category>database</category>
    </item>
  </channel>
</rss>
