<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Training Loop on Programmer.ie</title>
    <link>http://programmer.ie/tags/training-loop/</link>
    <description>Recent content in Training Loop on Programmer.ie</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 08 Aug 2026 12:40:00 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/training-loop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Are We Actually Doing?</title>
      <link>http://programmer.ie/books/pytorch-from-first-principles/01-chapter/</link>
      <pubDate>Sat, 08 Aug 2026 12:40:00 +0100</pubDate>
      <guid>http://programmer.ie/books/pytorch-from-first-principles/01-chapter/</guid>
      <description>&lt;p&gt;It has never been easier to obtain working PyTorch code. Describe a model to an assistant, paste the result into a file, and a training loop will usually appear and usually run. For a large fraction of everyday work this is fine, and this book does not ask you to pretend otherwise.&lt;/p&gt;&#xA;&lt;p&gt;The difficulty arrives afterwards.&lt;/p&gt;&#xA;&lt;p&gt;The code runs, but the loss sits at exactly the same value for two hundred steps. Or one tensor is &lt;code&gt;[32, 128]&lt;/code&gt; where the next operation wanted &lt;code&gt;[128, 32]&lt;/code&gt;. Or the gradient of a weight is &lt;code&gt;None&lt;/code&gt; and nothing says why. Or the model trained yesterday and today it does not, with no change you can point to. None of these are syntax errors. They do not produce a helpful traceback, and often they produce no traceback at all. They are questions about what the program is doing, and to answer them you need somewhere to look.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
