<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Torch-Compile on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/torch-compile/</link>
    <description>Recent content in Torch-Compile on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 30 Aug 2026 12:00:00 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/torch-compile/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Appendix A: PyTorch Diagnostic Field Guide</title>
      <link>http://programmer.ie/books/pytorch-from-first-principles/appendix-a/</link>
      <pubDate>Sun, 30 Aug 2026 12:00:00 +0100</pubDate>
      <guid>http://programmer.ie/books/pytorch-from-first-principles/appendix-a/</guid>
      <description>&lt;p&gt;This appendix introduces no new PyTorch mechanism.&lt;/p&gt;&#xA;&lt;p&gt;Everything here was earned earlier in the book by building something small, breaking it deliberately, measuring what changed, and locating the first place where reality stopped matching the intended computation.&lt;/p&gt;&#xA;&lt;p&gt;The purpose of this appendix is different.&lt;/p&gt;&#xA;&lt;p&gt;When a real model is failing, you usually do not need another explanation of autograd, broadcasting, attention or CUDA. You need to answer a narrower question:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
