<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: dijksterhuis</title><link>https://news.ycombinator.com/user?id=dijksterhuis</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 01 Nov 2026 02:09:15 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=dijksterhuis" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p>> The model weights change as the model goes through the training process.<p>Yes. They do. You are absolutely right about that.<p>But the <i>model architecture</i> doesn't change as a result of the training process. A piston doesn't suddenly turn into a digital watch as a result of tuning an engine. Similarly, the transformer part of a GPT model doesn't suddenly turn into something else as a result of optimizing a loss function.<p>---<p>i've got other stuff to do, so i'm stopping here.</p>
]]></description><pubDate>Sat, 05 Sep 2026 03:43:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=49572896</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49572896</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49572896</guid></item><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p>> Nobody says a system or product works a certain way and means the system while it's half built. "Bridges drop cars in the water!". Right.<p>To understand how an engine works, it's important to understand what a piston does as part of the engine.</p>
]]></description><pubDate>Sat, 05 Sep 2026 02:47:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=49572619</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49572619</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49572619</guid></item><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p>> The finished product is something which has been through post training.<p>again, <i>the finished product</i> wasn't what was discussed by GP, and you didn't clarify that you were switching to discussing RL (which is still probabilistic btw)</p>
]]></description><pubDate>Sat, 05 Sep 2026 02:21:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=49572485</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49572485</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49572485</guid></item><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p>> "it's not just a next-token predictor because a bunch of the training isn't about predicting the next token."<p><i>clever procedures</i> on top of the base transformer architecture.<p>i used simplified words/phrases to summarise the same thing you two were saying (the intent being: here's a version that may be digestible when discussing with others).<p>apparently that means i'm wrong though, no idea why because it seems you've decided to be dismissive rather than constructively elaborate on why this simplified and digestible version might be wrong :shrug:</p>
]]></description><pubDate>Sat, 05 Sep 2026 02:06:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=49572389</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49572389</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49572389</guid></item><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p>From GP, i.e. the context for <i>this local part of the thread</i><p>> Autoregressive LLMs generate tokens one at a time, disputing this is just plain wrong.<p>next-token prediction i.e. the bit built during pre-training.<p>at no point in your reply to GP did you specify that you were referring to post-training. respectfully, it seems like this one is on you pal :shrug:<p>> GPT-2 didn't use any reinforcement learning and is often given as a toy example. That release was 2019 and models now go through a various phases of training with different objective functions and optimizers.<p>yeah. so? the toy example works for pre-training. see above.</p>
]]></description><pubDate>Sat, 05 Sep 2026 01:49:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=49572306</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49572306</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49572306</guid></item><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p>they are <i>cleverly arranged / configured</i> next-most-likely-token predictors, possibly with some <i>clever procedures / attachments</i> on top.</p>
]]></description><pubDate>Sat, 05 Sep 2026 01:13:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=49572103</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49572103</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49572103</guid></item><item><title><![CDATA[New comment by dijksterhuis in "“Next-token predictor” is the wrong mental model for LLMs"]]></title><description><![CDATA[
<p><i>prediction</i> is a very specific term of art in the field of machine learning. generally speaking, machine learning models like LLMs are based on probability; performing a statistical prediction of the likely y given some input x<p><pre><code>    Probability(y | x)
</code></pre>
that's why we refer to outputs as a prediction. it is likelihoods and stuff. the output is never definitely correct as we're not dealing with heuristic processes.<p>> Prediction implies there is some "truth" or event or something that you can test against<p>there absolutely is a ground truth during training. the core predict-the-next-most-likely-token part of an LLM has a ground truth next-token. that's why you don't end up with generated text like: <i>fish spurious send cattle chocolate phone happy meaning ball orange board canada</i>.<p>> optimizes to predict the next token in training data<p>that is the optimization goal in training the next-most-likely-token core of an LLM, it basically translates to maximise the likelihood of predicting the next token x_i given the previous tokens<p><pre><code>    L(θ) = −log Π^n_{i=1} f_θ(x_i | x1, ..., x_{i−1})
</code></pre>
<a href="https://arxiv.org/pdf/2012.07805" rel="nofollow">https://arxiv.org/pdf/2012.07805</a> (GPT2 but the point still stands)<p>(edit: sorry for the ADHD edits)</p>
]]></description><pubDate>Sat, 05 Sep 2026 00:26:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=49571790</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49571790</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49571790</guid></item><item><title><![CDATA[New comment by dijksterhuis in "Discovery of a new OpenAI agent message board"]]></title><description><![CDATA[
<p>hn submission: <a href="https://news.ycombinator.com/item?id=49562744">https://news.ycombinator.com/item?id=49562744</a>  -- 84 points -- 67 comments</p>
]]></description><pubDate>Fri, 04 Sep 2026 15:41:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=49566221</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49566221</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49566221</guid></item><item><title><![CDATA[AI adoption at work is broad but shallow]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.theregister.com/ai-and-ml/2026/09/01/ai-adoption-at-work-is-broad-but-shallow/5293545">https://www.theregister.com/ai-and-ml/2026/09/01/ai-adoption-at-work-is-broad-but-shallow/5293545</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49563814">https://news.ycombinator.com/item?id=49563814</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 04 Sep 2026 12:47:15 +0000</pubDate><link>https://www.theregister.com/ai-and-ml/2026/09/01/ai-adoption-at-work-is-broad-but-shallow/5293545</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49563814</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49563814</guid></item><item><title><![CDATA[New comment by dijksterhuis in "The asteroid currently hitting front end web development"]]></title><description><![CDATA[
<p>if nobody owns the work, then anyone can take it from you.</p>
]]></description><pubDate>Fri, 04 Sep 2026 12:02:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=49563431</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49563431</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49563431</guid></item><item><title><![CDATA[New comment by dijksterhuis in "OpenAI agents hijacked German website in previously undisclosed AI breakout"]]></title><description><![CDATA[
<p>From the linked report<p>> The agents continue to poke around on DSEWiki. A few hours after they find the site, they start probing it for cross-site scripting (XSS) vulnerabilities. [...] The agent swarm starts testing whether they can execute JavaScript that they embed into the search page, and continue to do this for a few days<p>either the agents were doing free security testing for the site and “forgot” to submit a report, or they were trying XSS to gain something they didn’t have permission/authorization for.<p>also<p>> <i>Hijacking: To take control of (something) without permission or authorization and use it for one's own purposes</i>.<p>a mod had to go through and mass delete a bunch of pages that didn't belong on the site. no-one from the wiki site gave the agents permission to use their site as a message board. hijacking isn't being used here in the sense of "gained admin privileges to run crypto scripts" -- there are multiple ways to use a word.</p>
]]></description><pubDate>Fri, 04 Sep 2026 11:40:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=49563244</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49563244</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49563244</guid></item><item><title><![CDATA[New comment by dijksterhuis in "The asteroid currently hitting front end web development"]]></title><description><![CDATA[
<p>will not not necessarily be true for AI generated works in all territories<p><a href="https://news.ycombinator.com/item?id=49382041">https://news.ycombinator.com/item?id=49382041</a></p>
]]></description><pubDate>Fri, 04 Sep 2026 00:15:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=49558874</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49558874</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49558874</guid></item><item><title><![CDATA[New comment by dijksterhuis in "Malleable software = solid bases and custom code"]]></title><description><![CDATA[
<p>I had a great experience using $PROJECT_NAME. Another sentence that says nothing at all; but look, fancy and technically correct grammar use! You’re absolutely correct in agreeing with the author. Of course there’s an opposing point to consider — but that’s not it, this is.</p>
]]></description><pubDate>Mon, 31 Aug 2026 18:20:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=49512962</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49512962</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49512962</guid></item><item><title><![CDATA[New comment by dijksterhuis in "U.S. State Department pauses immigrant visa applications"]]></title><description><![CDATA[
<p>> should probably not be listened to<p>> a right to express their opinion<p>...</p>
]]></description><pubDate>Thu, 27 Aug 2026 12:17:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=49463540</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49463540</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49463540</guid></item><item><title><![CDATA[New comment by dijksterhuis in "U.S. State Department pauses immigrant visa applications"]]></title><description><![CDATA[
<p>couple of notes —<p>1a. Illegal immigration has nothing to do with visa based, legal immigration. illegal immigration is the type of immigration people are upset about here in the UK. most people have no problem with legal migration.<p>1b. anyone claiming the UK’s legal migration is any sort of problem right now, or in the past, should probably not be listened to in any way shape or form for anything they have to say on the matter.<p>2. a lot of the folks who have illegally entered the country end up asking for asylum, and by law their claims must be processed<p>3. the dublin convention states something along the lines of “asylum requests must be processed in the first EU country the person entered into”, ie it’s possible to remove people claiming asylum if they initially arrived in a different EU member state country<p>4. most people get to the uk having traveled through EU member states, because geography.<p>5. we left the EU, we cannot do 3 anymore. so we have a bunch of people stuck in hotels waiting for asylum claims to be processed.<p>illegal immigration got worse because we left the eu.</p>
]]></description><pubDate>Thu, 27 Aug 2026 11:11:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=49462874</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49462874</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49462874</guid></item><item><title><![CDATA[New comment by dijksterhuis in "Disruption with Some GitHub Services"]]></title><description><![CDATA[
<p>i'll echo this sentiment. historically there's been a lot more flexibility with GL CI yaml syntax, including <i>real</i> yaml anchors <a href="https://frenck.dev/github-actions-yaml-anchors-aliases-merge-keys/" rel="nofollow">https://frenck.dev/github-actions-yaml-anchors-aliases-merge...</a><p>sys-admin-ing gitlab can be a bit of a maze of web menus tho.</p>
]]></description><pubDate>Wed, 26 Aug 2026 19:35:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=49454601</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49454601</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49454601</guid></item><item><title><![CDATA[New comment by dijksterhuis in "How much of HN is AI?"]]></title><description><![CDATA[
<p>i feel the same way. there's nothing interesting or curious about someone writing prompts to outsource a bunch of effort/thinking/work off to some most likely continuation sequence predictor / set of most likely continuation sequence predictors.<p>i miss seeing clever and thrifty solutions to weird problems. hell, i miss people just doing plain weird shit and posting that.</p>
]]></description><pubDate>Wed, 26 Aug 2026 00:58:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=49442886</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49442886</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49442886</guid></item><item><title><![CDATA[New comment by dijksterhuis in "How much of HN is AI?"]]></title><description><![CDATA[
<p>i wouldn't mind one as well if at all possible?<p>a first look through the comments on some first page threads and they seem <i>far more thoughtful and considered</i>. it generally seems like a nicer commenting environment that might actually do me some good moving forward.</p>
]]></description><pubDate>Tue, 25 Aug 2026 23:58:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=49442410</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49442410</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49442410</guid></item><item><title><![CDATA[New comment by dijksterhuis in "Codefloe Is a Professionally Hosted Public Git Forge"]]></title><description><![CDATA[
<p>> Short version: We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.<p><a href="https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#o-disclaimer-of-warranties" rel="nofollow">https://docs.github.com/en/site-policy/github-terms/github-t...</a><p>> Short version: We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.<p><a href="https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#p-limitation-of-liability" rel="nofollow">https://docs.github.com/en/site-policy/github-terms/github-t...</a></p>
]]></description><pubDate>Mon, 24 Aug 2026 20:44:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=49425595</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49425595</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49425595</guid></item><item><title><![CDATA[New comment by dijksterhuis in "Thinking in Python"]]></title><description><![CDATA[
<p>Is it?</p>
]]></description><pubDate>Sun, 23 Aug 2026 01:01:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=49405356</link><dc:creator>dijksterhuis</dc:creator><comments>https://news.ycombinator.com/item?id=49405356</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49405356</guid></item></channel></rss>