<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Static-Analysis on Brian Faust</title><link>https://vacua.dev/tags/static-analysis/</link><description>Recent content in Static-Analysis on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vacua.dev/tags/static-analysis/rss.xml" rel="self" type="application/rss+xml"/><item><title>Static Analysis Turns Assumptions into Questions</title><link>https://vacua.dev/thoughts/static-analysis-turns-assumptions-into-questions/</link><pubDate>Sun, 01 Sep 2019 00:00:00 +0000</pubDate><guid>https://vacua.dev/thoughts/static-analysis-turns-assumptions-into-questions/</guid><description>&lt;p&gt;A domain action caught any exception and returned &lt;code&gt;false&lt;/code&gt;, &lt;code&gt;null&lt;/code&gt;, or an empty
array. Elsewhere, reusable services read the current request, tenant, and
locale from mutable framework context.&lt;/p&gt;
&lt;p&gt;Both patterns can be intentional. A fallback may be the contract at a
presentation boundary. Ambient context is normal in the code which receives a
web request. The problem appears when domain failure becomes indistinguishable
from a valid negative answer, or when a reusable service silently depends on
which request happened to call it.&lt;/p&gt;</description></item></channel></rss>