<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Making Contextual Decisions with Low Technical Debt · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1606.03966/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1606.03966/feed.xml" rel="self" type="application/rss+xml" /><item><title>Making Contextual Decisions with Low Technical Debt — mentioned by vii</title><link>https://news.ycombinator.com/item?id=24332686</link><guid isPermaLink="false">urn:hackerpapers:mention:1606.03966:24332686</guid><pubDate>Mon, 31 Aug 2020 15:54:52 GMT</pubDate><description>&lt;p&gt;The practices identified here make sense. Testing pipelines on a small amount of data to make sure there are not simple typos, then doing aggregate statistical tests and specific example condition tests will catch many issues. The paper &amp;quot;Making Contextual Decisions with Low Technical Debt&amp;quot; https://arxiv.org/pdf/1606.03966.pdf goes deeper. Testing and monitoring deployments are very similar. The idea of shadow testing new models (seeing how their outputs would differ from the production models on real data) has been very important for identifying issues in my experience. This can be…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1606.03966/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
