<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Smart "Predict, then Optimize" · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1710.08005/</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/1710.08005/feed.xml" rel="self" type="application/rss+xml" /><item><title>Smart "Predict, then Optimize" — mentioned by tikhonj</title><link>https://news.ycombinator.com/item?id=34928956</link><guid isPermaLink="false">urn:hackerpapers:mention:1710.08005:34928956</guid><pubDate>Fri, 24 Feb 2023 19:37:01 GMT</pubDate><description>&lt;p&gt;Honestly, the title threw me off at first—I used to work in supply chain optimization which very much follows a predict → optimize pattern, and I think there are interesting directions[1] for preferring a different approach, but the abstract and title made it pretty clear that the work focuses on a fundamentally different area. Supply chain forecasting is qualitatively different from the predictions in this essay because it applies to aggregate behavior, not to individuals. [1]: In particular, what we did (and what most people do?) is predict first, then optimize. Prediction and optimization…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1710.08005/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>math.OC</category></item></channel></rss>
