<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RLTF: Reinforcement Learning from Unit Test Feedback · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2307.04349/</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/2307.04349/feed.xml" rel="self" type="application/rss+xml" /><item><title>RLTF: Reinforcement Learning from Unit Test Feedback — mentioned by mkw5053</title><link>https://news.ycombinator.com/item?id=44953052</link><guid isPermaLink="false">urn:hackerpapers:mention:2307.04349:44953052</guid><pubDate>Tue, 19 Aug 2025 15:56:43 GMT</pubDate><description>&lt;p&gt;My stack lately has been Next.js with Prettier and very strict lint, type, and complexity gates, plus opinionated tests that aim for real signal over mere coverage theatre. I want to find the time to fine-tune GPT-4o using before/after examples of code that fails the gates and then passes them. The hope being it generates gate-compliant code on the first try much more often, which is cheaper and more reliable than relying on a base model with brute-force retries. I think this might also align with research showing that grounding models in execution feedback yields order-of-magnitude gains in…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2307.04349/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.AI</category></item></channel></rss>
