<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Development on Rusty Eddy</title><link>https://rustyeddy.com/software/</link><description>Recent content in Software Development on Rusty Eddy</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 31 May 2026 10:55:39 -0700</lastBuildDate><atom:link href="https://rustyeddy.com/software/index.xml" rel="self" type="application/rss+xml"/><item><title>Software is Hard</title><link>https://rustyeddy.com/software/software-is-hard/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/software-is-hard/</guid><description>A section opener explaining why software projects drift and how use cases, Kanban, testing, review, and release discipline make them predictable.</description></item><item><title>Use Cases</title><link>https://rustyeddy.com/software/use-cases/</link><pubDate>Fri, 27 Sep 2024 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/use-cases/</guid><description>&lt;h2 id="why-use-cases"&gt;Why Use Cases?&lt;/h2&gt;
&lt;p&gt;Before writing a single line of code, we need to understand what we are
building — and more importantly, &lt;em&gt;why&lt;/em&gt; someone would use it. Use cases give
us that foundation.&lt;/p&gt;
&lt;p&gt;A use case is a single, focused story that describes one way a user achieves
a specific goal with the system. Keep them in plain language, from the user&amp;rsquo;s
point of view, with no technical jargon. A good use case has a clear success
condition: you can observe or measure when it worked.&lt;/p&gt;</description></item><item><title>Use Cases to Tasks</title><link>https://rustyeddy.com/software/use-cases-to-tasks/</link><pubDate>Thu, 26 Dec 2024 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/use-cases-to-tasks/</guid><description>&lt;p&gt;A use case describes value from the user&amp;rsquo;s point of view. A task describes a
piece of work a developer can finish. Confusing those two is one of the
fastest ways to turn a software plan into a vague backlog.&lt;/p&gt;
&lt;p&gt;In &lt;a href="https://rustyeddy.com/software/use-cases/"&gt;Use Cases&lt;/a&gt; we turned Kelly&amp;rsquo;s watering-system story
into a focused use case:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;As a gardener, I want my system to periodically measure soil moisture and
turn on a water pump when the soil is dry, then turn it off when it gets
wet enough.&lt;/p&gt;</description></item><item><title>Organizing Software Projects with Kanban</title><link>https://rustyeddy.com/software/kanban/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/kanban/</guid><description>A practical guide to using Kanban cards, WIP limits, task sizing, and exit criteria to keep software projects visible and predictable.</description></item><item><title>Version Control Systems</title><link>https://rustyeddy.com/software/version-control-systems/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/version-control-systems/</guid><description>A practical guide to using Git history, branches, pull requests, and tags as the permanent record of a software project.</description></item><item><title>Test Driven Software Development</title><link>https://rustyeddy.com/software/test-driven-software-development/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/test-driven-software-development/</guid><description>A practical guide to test-driven development and the role of unit, integration, system, and acceptance tests in a reliable release process.</description></item><item><title>Peer Reviews</title><link>https://rustyeddy.com/software/peer-review/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/peer-review/</guid><description>A practical guide to code review: what authors should prepare, what reviewers should check, and how pull requests fit into release quality.</description></item><item><title>Wireframes and Storyboards</title><link>https://rustyeddy.com/software/wireframes-and-storyboards/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/wireframes-and-storyboards/</guid><description>A practical guide to using storyboards for user flows and wireframes for screen decisions before implementation begins.</description></item><item><title>Release Process</title><link>https://rustyeddy.com/software/release-process/</link><pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/release-process/</guid><description>A practical release process for turning reviewed and tested code into versioned, recoverable software artifacts.</description></item><item><title>Fixed-Point Numeric Types in Go Financial Software</title><link>https://rustyeddy.com/software/numeric-types-financial-software/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/numeric-types-financial-software/</guid><description>A practical guide to fixed-point arithmetic in Go for prices, money, pips, API boundaries, and trading-system correctness.</description></item><item><title>The Strategy Pattern in a Backtesting Engine</title><link>https://rustyeddy.com/software/strategy-pattern-backtesting/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/software/strategy-pattern-backtesting/</guid><description>A practical design for keeping trading strategy logic portable across backtests and live execution by returning plans instead of touching brokers directly.</description></item></channel></rss>