<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nicholas FitzRoy-Dale</title>
    <link>https://nfd.world/blog.html</link>
    <atom:link href="https://nfd.world/rss.xml" rel="self" type="application/rss+xml" />
    <description>Computers, their problems, and how to fix them.</description>
    <language>en</language>
    <lastBuildDate>Sat, 26 Sep 2026 01:54:00 +0000</lastBuildDate>
    <item>
      <title>RAM training</title>
      <link>https://nfd.world/blog/ram-training.html</link>
      <guid isPermaLink="true">https://nfd.world/blog/ram-training.html</guid>
      <pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate>
      <description>If the history of DRAM were a drama series, every increase in capacity would be stalked by that monster of complexity, speed. Up until, say, the 80s, RAM was sufficiently slow that it could be characterised by a couple of numbers. Now, though, it&#39;s fast enough that physical limits, such as the speed of light, are an important part of the design process. At the speeds that DRAM operates nowadays, the wires representing the connection between DRAM and its controller behave less like an instantaneous transport of signal and more like a series of crowded parallel shipping lanes, where individual bits move leisurely to their destination, some arriving sooner than others, interfering with their neighbors, and bouncing off the dock.</description>
    </item>
  </channel>
</rss>