<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Selectivity on SoftDevStudio.com</title>
    <link>https://softdevstudio.com/tags/selectivity/</link>
    <description>Recent content in Selectivity on SoftDevStudio.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://softdevstudio.com/tags/selectivity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Selectivity Adds Practical Examples for CSV and JSON Lines</title>
      <link>https://softdevstudio.com/selectivity-adds-practical-examples-for-csv-and-json-lines/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/selectivity-adds-practical-examples-for-csv-and-json-lines/</guid>
      <description>&lt;p&gt;Selectivity now has three more runnable examples showing how a developer can put the Go reducer to work. Each pairs a generated input with a Python predicate and a saved run from the released 0.1.1 binary. The engine has not changed. The new material makes the contract easier to inspect: define the behavior worth keeping, classify invalid candidates honestly and keep the run evidence beside the small result.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://selectivity.net/selectivity-finds-the-two-csv-records-behind-a-calculation-bug/&#34;&gt;CSV example&lt;/a&gt; reduces an export to its header and the discount-refund pair behind a deliberately introduced accounting error. The &lt;a href=&#34;https://selectivity.net/selectivity-isolates-numeric-precision-loss-in-json-lines/&#34;&gt;JSON Lines example&lt;/a&gt; isolates one identifier that changes after a lossy numeric conversion. These are controlled fixtures, with three observations per candidate. Their posts explain which statements the successful reductions support and why an unresolved validity check can prevent a minimality claim.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Selectivity Shrinks Failing Inputs Into Smaller Bug Reports</title>
      <link>https://softdevstudio.com/selectivity-shrinks-failing-inputs-into-smaller-bug-reports/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/selectivity-shrinks-failing-inputs-into-smaller-bug-reports/</guid>
      <description>&lt;p&gt;Selectivity joins the studio with a small, practical job: reduce the input that triggers a bug while a command checks that the behavior survives. The first release works on file lines and directory contents, with an optional line pass inside the files that remain. Each predicate observation gets a fresh copy, and ambiguous outcomes leave the earlier input in place. The &lt;a href=&#34;https://selectivity.net/selectivity-reduces-failing-inputs-and-records-every-candidate-check/&#34;&gt;project introduction&lt;/a&gt; explains the contract.&lt;/p&gt;&#xA;&lt;p&gt;Two generated examples give the first version a clear check. A 20000-line file becomes its two required trigger lines, and a three-file bundle becomes two files containing only their required lines. These are known-answer fixtures, rather than performance claims about real bugs. The &lt;a href=&#34;https://selectivity.net/selectivity-reduces-a-generated-file-from-20000-lines-to-two/&#34;&gt;line case&lt;/a&gt; and &lt;a href=&#34;https://selectivity.net/selectivity-reduces-a-configuration-bundle-by-files-and-lines/&#34;&gt;directory case&lt;/a&gt; include the limits, and the &lt;a href=&#34;https://selectivity.net/demo/&#34;&gt;browser playback&lt;/a&gt; steps through the actual recorded checks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
