<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SoftDevStudio.com</title>
    <link>https://softdevstudio.com/</link>
    <description>Recent content on SoftDevStudio.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://softdevstudio.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Studio Roundup: Nine BareProxy Plugins, VPN Works 0.6.0 and What Six Other Projects Have Shipped</title>
      <link>https://softdevstudio.com/studio-roundup-nine-bareproxy-plugins-vpn-works-0.6.0-and-what-six-other-projects-have-shipped/</link>
      <pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/studio-roundup-nine-bareproxy-plugins-vpn-works-0.6.0-and-what-six-other-projects-have-shipped/</guid>
      <description>&lt;p&gt;The studio&amp;rsquo;s eight projects went public between late September and early October, and each one has a release on GitHub now. This first note gathers their progress up to 14 October, with links to each project&amp;rsquo;s own posts for the detail. From here on, notes will follow the releases as they come.&lt;/p&gt;&#xA;&lt;p&gt;All eight release the same way. A push to main runs the project&amp;rsquo;s tests. If they pass and the version number has gone up, a workflow builds the release and publishes it. Nobody does that part by hand, so a release can go out the day its work is done.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>https://softdevstudio.com/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/about/</guid>
      <description>&lt;p&gt;SoftDevStudio.com is a small, independent software studio. We build databases, job queues, proxies and network tools, mostly in Go, and the code of our own projects is on GitHub under Apache 2.0.&lt;/p&gt;&#xA;&lt;h2 id=&#34;small-software-on-purpose&#34;&gt;Small Software, on Purpose&lt;/h2&gt;&#xA;&lt;p&gt;Most of our projects follow the SQLite pattern. One small core does one job and ships as a single file or binary, with no fleet of services around it. That keeps it cheap to run and easy to hand over, which matters when the code is going to be yours.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contact</title>
      <link>https://softdevstudio.com/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/contact/</guid>
      <description>&lt;p&gt;Email the studio at &lt;a href=&#34;mailto:info@softdevstudio.com&#34;&gt;info@softdevstudio.com&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Tell us what you want built and what it has to run on. A deadline or a budget helps if you have one, and so do links to any code or prototype that already exists.&lt;/p&gt;&#xA;&lt;p&gt;Questions about one of our open source projects are best asked on that project&amp;rsquo;s GitHub issue tracker. You&amp;rsquo;ll find the links on the &lt;a href=&#34;https://softdevstudio.com/work/&#34;&gt;Work&lt;/a&gt; page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Services</title>
      <link>https://softdevstudio.com/services/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/services/</guid>
      <description>&lt;p&gt;We take on the work where a small team that writes careful code makes the difference: a first version that has to hold up in front of users, or a system that has to stay small and fast.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-we-take-on&#34;&gt;What We Take On&lt;/h2&gt;&#xA;&lt;div class=&#34;breakout&#34;&gt;&#xA;&#xA;&lt;div class=&#34;services&#34;&gt;&#xA;  &lt;article class=&#34;service&#34;&gt;&#xA;    &lt;p class=&#34;service-index&#34;&gt;01&lt;/p&gt;&#xA;    &lt;h3 class=&#34;service-name&#34;&gt;Prototypes and MVPs&lt;/h3&gt;&#xA;    &lt;p class=&#34;service-text&#34;&gt;A working first version you can put in front of users or investors. We find the smallest build that proves the idea, and build that first.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Work</title>
      <link>https://softdevstudio.com/work/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/work/</guid>
      <description>&lt;p&gt;These are the studio&amp;rsquo;s own projects. All of them are open source under Apache 2.0, each with a site of its own and its code on GitHub. Most are early 0.x releases, and each README says what works today. Read the code before you hire us.&lt;/p&gt;&#xA;&lt;div class=&#34;breakout&#34;&gt;&#xA;&#xA;&lt;div class=&#34;projects projects-list&#34;&gt;&#xA;  &lt;article class=&#34;project&#34;&gt;&#xA;    &lt;div class=&#34;project-id&#34;&gt;&#xA;      &lt;p class=&#34;project-meta&#34;&gt;&lt;span class=&#34;project-index&#34;&gt;01&lt;/span&gt;&lt;span class=&#34;project-kind&#34;&gt;Database &amp;middot; C&lt;/span&gt;&lt;/p&gt;&#xA;&lt;h2 class=&#34;project-name&#34;&gt;&lt;a href=&#34;https://altsql.com&#34;&gt;AltSql&lt;/a&gt;&lt;/h2&gt;&#xA;&#xA;      &lt;p class=&#34;project-links&#34;&gt;&lt;a href=&#34;https://altsql.com&#34; aria-label=&#34;AltSql site, altsql.com&#34;&gt;altsql.com&lt;span class=&#34;ext&#34; aria-hidden=&#34;true&#34;&gt;&amp;#8599;&lt;/span&gt;&lt;/a&gt;&lt;a href=&#34;https://github.com/AltSql/altsql&#34; aria-label=&#34;AltSql on GitHub&#34;&gt;GitHub&lt;span class=&#34;ext&#34; aria-hidden=&#34;true&#34;&gt;&amp;#8599;&lt;/span&gt;&lt;/a&gt;&#xA;&lt;/p&gt;&#xA;&#xA;    &lt;/div&gt;&#xA;    &lt;div class=&#34;project-body&#34;&gt;&#xA;      &lt;p class=&#34;project-line&#34;&gt;A native hybrid of key-value and SQL, from the sensor to the gateway. Both ends share the same records, byte for byte.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
