<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Case Studies on Brian Faust</title><link>https://wimdy.works/case-studies/</link><description>Recent content in Case Studies on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 30 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wimdy.works/case-studies/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Rating Engine That Outgrew Its First Design</title><link>https://wimdy.works/case-studies/building-a-pricing-engine/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><guid>https://wimdy.works/case-studies/building-a-pricing-engine/</guid><description>&lt;p&gt;The first version could calculate the prices. That wasn&amp;rsquo;t the same as having
a good representation of the price book, or an affordable way to evaluate it.
Those distinctions drove most of the interesting work on this project—well
before changing languages became the next decision.&lt;/p&gt;
&lt;p&gt;I built a private logistics rating engine which could express different
tariffs without adding a new application branch for every combination. It
stayed private rather than becoming a commercial product. It was still one
of the most satisfying systems I&amp;rsquo;ve worked on: the complexity largely belonged
to the problem itself. I wasn&amp;rsquo;t first trying to explain years of
unrelated exceptions which had somehow become permanent business rules.&lt;/p&gt;</description></item></channel></rss>