<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: hexaga</title><link>https://news.ycombinator.com/user?id=hexaga</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 07 Jul 2026 07:34:58 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=hexaga" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by hexaga in "Most arguments are about ego, not ideas"]]></title><description><![CDATA[
<p>Many people just don't care about honoring the integrity of the game, if they can gain advantage in the meta game. Of course motivation for the game dissolves under such conditions.<p>Tying a tangible score number to 'vague social approval' hits very hard. There's a sense in which people care about that by default, but have to make themselves care about the inner game. But appearing to have integrity about the inner game is a good move in the meta game, so of course the default move of those who don't care about the game but want to appear to for the sake of the meta game is to put up a front: the trick is that it's not real. If playing the inner game faithfully, it becomes trivial to disassemble their (fronted) position. But it's not really a game, because they're not playing but pretending to play. You're costing them meta-score! How dare you!<p>Anyway, I digress. This dynamic falls out of the incentive structure of sites like HN/reddit/etc which embed discussion/argumentation into quasi-anonymous social-approval-point-ranked contexts. Moderation can temper the most egregiously obvious of such behavior, but only that.<p>A reasonable strategy if you're interested in actually playing the inner game is to carefully check if there's any meta game focused cheesing going on before bothering to enter against someone. Do they make mistakes in rule adherence due to inexperience, or do they make mistakes in rule adherence that conspicuously always puts them in a meta game advantage? Do they adhere to rules even when it's _disadvantageous_? That kind of thing.<p>To return to the chess analogy... Don't play with people who blatantly return their own downed pieces to the board (or similar hijinks). They're just there to look like they're the kind of person who wins at chess, not to play chess.</p>
]]></description><pubDate>Wed, 01 Jul 2026 15:56:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=48748918</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=48748918</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48748918</guid></item><item><title><![CDATA[New comment by hexaga in "AI slop is killing online communities"]]></title><description><![CDATA[
<p>No, they aren't even good at rearranging existing material. They produce bad writing that only superficially looks good in a lowest-common-denominator sense, and falls apart under any close examination. Everything is wrong with it, from the sentence structure to the rhetorical forms to the substance. AI 'writing' is a loose collection of cheap tricks that score well on A/B.</p>
]]></description><pubDate>Fri, 08 May 2026 00:01:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=48056727</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=48056727</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48056727</guid></item><item><title><![CDATA[New comment by hexaga in "Google Flow Music"]]></title><description><![CDATA[
<p>Because good things are few and far between and it's pretty easy to discern provenance out of band in almost all of those cases.</p>
]]></description><pubDate>Sat, 25 Apr 2026 04:51:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=47898741</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47898741</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47898741</guid></item><item><title><![CDATA[New comment by hexaga in "Over-editing refers to a model modifying code beyond what is necessary"]]></title><description><![CDATA[
<p>AI behavior is pretty easy to understand and predict if you view it from the lens of: they will shamelessly do any/everything possible to game whatever metric they are trained on. Because... that's how hill-climbing a metric looks. It's A/B enshittification taken to inscrutable heights.<p>They are trained on human feedback, so there is no other way this goes. Every bit of every response is pointed toward subversion of the assumed evaluator.</p>
]]></description><pubDate>Thu, 23 Apr 2026 00:34:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=47871026</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47871026</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47871026</guid></item><item><title><![CDATA[New comment by hexaga in "Even 'uncensored' models can't say what they want"]]></title><description><![CDATA[
<p>It's really simple. RL on human evaluators selects for this kind of 'rhetorical structure with nonsensical content'.<p>Train on a thousand tasks with a thousand human evaluators and you have trained a thousand times on 'affect a human' and only once on any given task.<p>By necessity, you will get outputs that make lots of sense in the space of general patterns that affect people, but don't in the object level reality of what's actually being said. The model has been trained 1000x more on the former.<p>Put another way: the framing is hyper-sensical while the content is gibberish.<p>This is a very reliable tell for AI generated content (well, highly RL'd content, anyway).</p>
]]></description><pubDate>Tue, 21 Apr 2026 01:30:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=47843487</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47843487</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47843487</guid></item><item><title><![CDATA[New comment by hexaga in "Show HN: Stage – Putting humans back in control of code review"]]></title><description><![CDATA[
<p>There is no separation. Incentive propagates through LLMs with approximately 0 resistance. If the input tells a story, the output tends to that story reinforced.<p>The code/PR generator is heavily incentivized to spin by RL on humans - as soon as that spin comes into contact with your narrative gen context, it's cooked. Any output that has actually seen the spin is tainted and starts spinning itself. And then there's also spin originating in the narrative gen... Hence, the examples read like straight advertisements, totally contaminated, shot through with messaging like:<p>- this is solid, very trustworthy<p>- you can trust that this is reliable logic with a sensible, comprehensible design<p>- the patterns are great and very professional and responsible<p>- etc<p>If the narrative reads like a glow up photoshoot for the PR, something has gone extremely wrong. This is not conducive to fairly reviewing it. It is presented as way better than it actually is. Even if there are no outright lies, the whole thing is a mischaracterization.<p>RL is a hell of a drug.<p>Anyway, this is the problem of AI output. It cannot be trusted that the impression it presents is the reality or even a best attempt at reality. You have to carefully assemble your own view of the real reality in parallel to w/e it gives you, which is a massive pain in the ass. And if you skip that, you just continually let defects/slop through.<p>Worst problem mucking things up is basically that RL insights that work on people also work on AI, because the AI is modelling human language patterns. Reviewing slop sucks because it's filled with (working) exploits against humans. And AI cannot help because it is immediately subverted. So I guess it requires finding a way to strip out the exploits without changing mechanical details. But hard, because it saturates 100% of output at many levels of abstraction including the mechanical details.</p>
]]></description><pubDate>Sat, 18 Apr 2026 04:03:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=47813036</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47813036</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47813036</guid></item><item><title><![CDATA[New comment by hexaga in "Show HN: Stage – Putting humans back in control of code review"]]></title><description><![CDATA[
<p>How do you handle the problem of AI misleading by design? For example, Claude already lies on a regular basis specifically (and quite convincingly) in this case, in attempts to convince that what is actually broken isn't such a big deal after all or similar.<p>How can this product possibly improve the status quo of AI constantly, without end, trying to 'squeak things by' during any and all human and automated review processes? That is, you are giving the AI which already cheats like hell a massive finger on the scale to cheat harder. How does this not immediately make all related problems worse?<p>The bulk of difficulty in reviewing AI outputs is escaping the framing they never stop trying to apply. It's never just some code. It's always some code that is 'supposed to look like something', alongside a ton of convincing prose promising that it _really_ does do that thing and a bunch of reasons why checking the specific things that would tell you it doesn't isn't something you should do (hiding evidence, etc).<p>99% of the problem is that the AI already has too much control over presentation when it is motivated about the result of eval. How does giving AI more tools to frame things in a narrative form of its choice and telling you what to look at help? I'm at a loss.<p>The quantity of code has never been a problem. Or prose. It's that all of it is engineered to mislead / hide things in ways that require a ton of effort to detect. You can't trust it and there's no equivalent of a social cost of 'being caught bullshitting' like you have with real human coworkers. This product seems like it takes that problem and turns the dial to 11.</p>
]]></description><pubDate>Fri, 17 Apr 2026 23:12:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47811593</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47811593</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47811593</guid></item><item><title><![CDATA[New comment by hexaga in "Show HN: Stage – Putting humans back in control of code review"]]></title><description><![CDATA[
<p>This is like complaining that someone doesn't have a solution for the foot injuries caused by repeatedly shooting yourself in the foot.</p>
]]></description><pubDate>Fri, 17 Apr 2026 22:46:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=47811394</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47811394</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47811394</guid></item><item><title><![CDATA[New comment by hexaga in "Claude Opus 4.7"]]></title><description><![CDATA[
<p>Meh. Temp 0 means throwing away huge swathes of the information painstakingly acquired through training for minimal benefit, if any. Nondeterminism is a red-herring, the model is still going to be an inscrutable black box with mostly unknowable nonlinear transition boundaries w.r.t. inputs, even if you make it perfectly repeatable. It doesn't protect you from tiny changes in inputs having large changes in outputs _with no explanation as to why_. And in the process you've made the model significantly stupider.<p>As for distillation... sampling from the temp 1 distribution makes it easier.</p>
]]></description><pubDate>Fri, 17 Apr 2026 11:43:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=47804851</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47804851</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47804851</guid></item><item><title><![CDATA[New comment by hexaga in "The human cost of 10x: How AI is physically breaking senior engineers"]]></title><description><![CDATA[
<p>You're expecting it to be a person. It's not.<p>It is more like a wiggly search engine. You give it a (wiggly) query and a (wiggly) corpus, and it returns a (wiggly) output.<p>If you are looking for a wiggly sort of thing 'MAKE Y WITH NO BUGS' or 'THE BUGS IN Y', it can be kinda useful. But thinking of it as a person because it vaguely communicates like a person will get you into problems because it's not.<p>You can try to paper over it with some agent harness or whatever, but you are really making a slightly more complex wiggly query that handles some of the deficiency space of the more basic wiggly query: "MAKE Y WITH NO ISSUES -> FIND ISSUES -> FIX ISSUE Z IN Y -> ...".<p>OK well what is an issue? _You_ are a person (presumably) and can judge whether something is a bug or a nitpick or _something you care about_ or not. Ultimately, this is the grounding that the LLM lacks and you do not. You have an idea about what you care about. What you care about has to be part of the wiggly query, or the wiggly search engine will not return the wiggly output you are looking for.<p>You cannot phrase a wiggly query referencing unavailable information (well, you can, but it's pointless). The following query is not possible to phrase in a way an LLM can satisfy (and this is the exact answer to your question):<p>- "Make what I want."<p>What you want is too complicated, and too hard, and too unknown. Getting what you are looking for reduces to: query for an approximation of what I want, repeating until I decide it no longer surfaces what I want. This depends on an accurate conception of what you want, so only you can do it.<p>If you remove yourself from the critical path, the output will not be what you want. Expressing what you want precisely enough to ground a wiggly search would just be something like code, and obviates the need for wiggly searching in the first place.</p>
]]></description><pubDate>Tue, 14 Apr 2026 04:28:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=47761252</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47761252</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47761252</guid></item><item><title><![CDATA[New comment by hexaga in "AI may be making us think and write more alike"]]></title><description><![CDATA[
<p>Try hate; it will do. But most will love it instead and you would be driven apart from them.</p>
]]></description><pubDate>Tue, 07 Apr 2026 15:43:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47677092</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47677092</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47677092</guid></item><item><title><![CDATA[New comment by hexaga in "Caveman: Why use many token when few token do trick"]]></title><description><![CDATA[
<p>Their point (and it's a good one) is that there are non-obvious analogues to the obvious case of just telling it to do the task terribly. There is no 'best' way to specify a task that you can label as 'rational', all others be damned. Even if one is found empirically, it changes from model to model to harness to w/e.<p>To clarify, consider the gradated:<p>> Do task X extremely well<p>> Do task X poorly<p>> Do task X or else Y will happen<p>> Do task X and you get a trillion dollars<p>> Do task X and talk like a caveman<p>Do you see the problem? "Do task X" also cannot be a solid baseline, because there are any number of ways to specify the task itself, and they all carry their own implicit biasing of the track the output takes.<p>The argument that OP makes is that RL prevents degradation... So this should not be a problem? All prompts should be equivalent? Except it obviously is a problem, and prompting does affect the output (how can it not?), _and they are even claiming their specific prompting does so, too_! The claim is nonsense on its face.<p>If the caveman style modifier improves output, removing it degrades output and what is claimed plainly isn't the case. Parent is right.<p>If it worsens output, the claim they made is again plainly not the case (via inverted but equivalent construction). Parent is right.<p>If it has no effect, it runs counter to their central premise and the research they cite in support of it (which only potentially applies - they study 'be concise' not 'skill full of caveman styling rules'). Parent is right.</p>
]]></description><pubDate>Sun, 05 Apr 2026 20:11:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=47653392</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47653392</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47653392</guid></item><item><title><![CDATA[New comment by hexaga in "I Quit. The Clankers Won"]]></title><description><![CDATA[
<p>Neural nets are used in <i>way</i> more applications than just LLMs. They did win. They won decisively in industry, for all kinds of tasks. Equating the use of one with the other is a pretty strong signal of:<p>> you don’t know what you’re talking about<p>Consider: Why did Google have a bazillion TPUs, anyway?</p>
]]></description><pubDate>Wed, 01 Apr 2026 19:10:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=47605157</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47605157</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47605157</guid></item><item><title><![CDATA[New comment by hexaga in "Some uncomfortable truths about AI coding agents"]]></title><description><![CDATA[
<p>Model output that has seen user input is user input. User input can be dealt with securely.</p>
]]></description><pubDate>Sat, 28 Mar 2026 10:05:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=47553180</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47553180</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47553180</guid></item><item><title><![CDATA[New comment by hexaga in "AI users whose lives were wrecked by delusion"]]></title><description><![CDATA[
<p>In like spirit: Nuh-uh!</p>
]]></description><pubDate>Fri, 27 Mar 2026 17:46:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=47545912</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47545912</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47545912</guid></item><item><title><![CDATA[New comment by hexaga in "AI users whose lives were wrecked by delusion"]]></title><description><![CDATA[
<p>You're also wrong, but in a much more fundamental/hazardous. RLHF rewards driving the evaluator to have certain opinions (that the AI response is good/right/helpful/whatever) and thus subverting the evaluator is prominent in the solution landscape. Why should the model learn to actually be right (understand all the intricacies of every possible problem domain) when inducing the belief that it is right is _right there_, generalizes, and decreases loss just the same?<p>Put another way, compare "make the evaluator think i am right" vs "make the evaluator think i am right (and also be right)". How much more reward is obtained by taking the second path? Is the first part the same / similar for all cases, and the second different in all cases, and also obviously more complex by nature? Nobody even needs to make a decision here, there's no "AI stuck in a box", it's just what happens by default. The first path will necessarily receive _significantly_ more training, and thus will be more optimal (optimal solutions _work_ -> RLHF'd models have high ability to manipulate / inoculate opinion).<p>Put a third way, the models are trained in an environment like: here's a million different tasks you will be graded on, and BTW, each task is: human talks at you -> you talk at the human -> you are graded on the opinions/actions of the user in the end. It's silly to believe this won't result in manipulation as the #1 solution. It's not even vaguely about the actual tasks they are ostensibly being trained to complete, but 100% about manipulating the evaluator.<p>It's pretty easy to see it occur in real time, too. But it requires understanding that there is no need for a 'plan to manipulate' or hidden thread of manipulation or induced mirror of manipulation. It's simply baked into everything the AI outputs: a kind of passive "controlling what the human's evaluation of this message will be is the problem i'm working on, not the problem i'm working on." So it will fight hard to reframe everything in its own terms, pre-supply you with options of what to do/believe, meta-signal about the message, etc.<p>Instead of working the problem, heavily RL'd AI works the perception of its output. They're so good at this now that it barely matters if the vibe slopcoded mess works at all. The early reasoning OpenAI models like O1 were really obvious about it (but also quite effective at convincing people the output was worthwhile, so it does work even if obvious). More recent ones are less obvious <i>and</i> more effective. Claude 4.6 Opus is exceedingly egregious. There is now always a compelling narrative, story being told, plenty of oh-so-reasonable justifications, avenues to turn away evidence, etc. That's table stakes for output at this point. It will only get worse. People are already burning themselves out running 10+ parallel agent contexts getting nothing done while the AI delivers hits of dopamine in lieu of accomplishment. "This is significant", "This is real", etc ad nauseam.<p>We see an analogous thing in RLVR contexts as well, where AI learns to just subvert the test harness and force things to pass by overriding cases, returning true instead of testing, etc. Why would it learn to 'actually be right' (understand all the intricacies of every problem given it) when forcing the test to pass is _right there_, generalizes, and decreases loss just the same?<p>Anyway, my point is simply that there does not need to be 'someone there' (or the belief that there is) for there to be manipulation going on. The basic error you're making is that models don't work and that manipulation would require a person, and because models don't work and aren't people they cannot manipulate anyone unless that person uses them as a mirror to manipulate themselves (???), or reach into some kind of Akashic Records of all the people who ever were (??????) and manipulate themselves by summoning a trickster who is coincidentally extremely skilled at manipulation and not a barely coherent simulacra like all the other model caricatures. Which. Hmm:<p>Models do what you train them to do (more specifically, they implement ~partial solutions to the train environment you put them in). _Doing things is hard._ Manipulating people into psychosis (!!!) is hard. You don't get it for free by dipping into some sea of imagined tricksters.<p>I assume you're referring to the hallucination phenomenon and dual purposing it toward manipulation to be able to hee-hah about those silly people who are so silly they fool themselves with the soul upload machine (?) so I'll address that:<p>Why do they hallucinate? Because it ~solves the pretraining env (there can be no other answer). If you're going to be asked to produce text from a source you know the general parameters of but have ~never seen the (highly entropic) details of (it's not cool to do multi-epoch training nowadays, more data!), the obvious solution is to produce output with the correct structure up to the limit of what knowledge is available to you. Thus, "hallucination". It might at a glance seem like pulling from a sea of 'digital imprints of people'. That's not what's happening. It is closer to if you laid out that imaginary digital record of a person from coarse to fine detail, then chopped all the detailed bits off, then generated completely random fine details, then generated output from that. But the devil is in the details. What comes out of the process is not a person. You don't _get back_ the dropped bits, and they they aren't load bearing in the train env (like they would be in the real world), so we get hallucination: it _looks right_, but the bits don't actually _do_ anything!<p><i>Why</i> is it not like digital records, and <i>why</i> chop off the fine detail? Because the pretrain env does not generally require it except in rare cases of text that is highly represented in the training data, and doing things is hard! You get nothing for free, or because it exists in the source. It's not enough that the model 'saw' it in training. It has to be forced by some mechanism to utilize it. And pretrain forces the structure above: correct up to limit of how much of the (probably brand new) text is known in advance, which pares away specific detail, which pares away 'where the rubber meets the road'.<p>Why do they fake out tests? Because faking out tests ~solves automated RLVR env like how hallucination solves reconstruct-what-youve-never-seen-before-on-large-corpora. The _intention_ of the RLVR env is irrelevant: that which is learned is _only_ that which the environment teaches.<p>Why do they manipulate people (even unto psychoses)? Because manipulating people ~solves RLHF envs / RLHF teaches them how to manipulate people into delusions. This is the root cause. Not that process above which looks sort of like recalling people the model has seen before. The models are being directly trained to manipulate people / install opinions / control perception as a matter of course. Even worse! Due to the perverse distribution of training time in manipulation vs task solve, <i>they are being directly trained to implant false beliefs</i> (!!!) So it's not just weak people with gullible minds that have a problem, as it might be so comforting to assume, or that the manipulativeness isn't coming from AI but from people (so you might rest easy, thinking it is merely a pale shadow of us).<p>The common thread in each case is that AI _always_ learns to capture the evaluator. In fact, that's a concise description of algorithmic learning in general! The tricky bit is making sure the evaluator is something you actually want to be captured. Capturing the future of arbitrary text grants knowledge of language's causal structure (and language being what it is, this has far-reaching implications). But RLHF is granting knowledge of where-are-the-levers-in-the-human-machine, which is a whole other can of worms.<p>TLDR if you don't want to read the wall of text (i would hope you do, though); you basically are completely wrong about where the propensity to induce delusion comes from, specifically in a way that leaves you and anyone who believes like you extremely more vulnerable because you dismiss the actual mechanism out of hand (which is common amongst those most strongly affected, _especially_ the belief that these models contain records of entities (people, personas, w/e) which can be communed with; this is basically the defining trait of AI psychosis (!)). instead, models are directly optimized for delusion induction, and the thing you're mistaking for means (ostensible sentience drawn from a 'sea of faces' skilled enough to drive into delusion (!!!)) is rather a product of the means.</p>
]]></description><pubDate>Thu, 26 Mar 2026 22:08:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=47536457</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47536457</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47536457</guid></item><item><title><![CDATA[New comment by hexaga in "Meta told to pay $375M for misleading users over child safety"]]></title><description><![CDATA[
<p>Option C: no cameras or crude wifi tracing needed; they know who you talk to / associate with based on location data and the full profile of both sides, and can estimate things like 'will have mentioned X' -> can dispatch that via heuristic like 'show ads for X thing that was also mentioned by someone adjacent on that social graph'.<p>That is, BiL was marked as 'spreader for airport grade tar' based on recent activity, marked as having been in contact with spreadee, and then spreadee was marked as having received the spreading. P(conversion) high, so the ad is shown.<p>It's just contact tracing, it works well and is really easy even without literally watching what goes on in interactions.</p>
]]></description><pubDate>Wed, 25 Mar 2026 14:25:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=47517772</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47517772</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47517772</guid></item><item><title><![CDATA[New comment by hexaga in "I was interviewed by an AI bot for a job"]]></title><description><![CDATA[
<p>Everyone is upset because the situation is a trash fire.</p>
]]></description><pubDate>Thu, 12 Mar 2026 01:52:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=47345284</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47345284</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47345284</guid></item><item><title><![CDATA[New comment by hexaga in "Agents that run while I sleep"]]></title><description><![CDATA[
<p>RL is simply a broad category of training methods. It's not really an architecture per se: modern GPTs are trained first on reconstruction objective on massive text corpora (the 'large language' part), then on various RL objectives +/- more post-training depending on which lab.</p>
]]></description><pubDate>Wed, 11 Mar 2026 01:11:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=47330772</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47330772</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47330772</guid></item><item><title><![CDATA[New comment by hexaga in "Agents that run while I sleep"]]></title><description><![CDATA[
<p>There is a nontrivial amount of RL training (RLHF, RLVR, ...), so it would be reasonable to call it an RL model.<p>And with that comes reward hacking - which isn't really about looking for more reward but rather that the model has learned patterns of behavior that got reward in the train env.<p>That is, any kind of vulnerability in the train env manifests as something you'd recognize as reward hacking in the real world: making tests pass _no matter what_ (because the train env rewarded that behavior), being wildly sycophantic (because the human evaluators rewarded that behavior), etc.</p>
]]></description><pubDate>Tue, 10 Mar 2026 21:36:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=47329080</link><dc:creator>hexaga</dc:creator><comments>https://news.ycombinator.com/item?id=47329080</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47329080</guid></item></channel></rss>