<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CPU on The TARDIS Server Project</title><link>https://tardisgallifrey.codeberg.page/tags/cpu/</link><description>Recent content in CPU on The TARDIS Server Project</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 15 Aug 2026 11:52:24 -0500</lastBuildDate><atom:link href="https://tardisgallifrey.codeberg.page/tags/cpu/index.xml" rel="self" type="application/rss+xml"/><item><title>Computer architecture</title><link>https://tardisgallifrey.codeberg.page/posts/archcomp/</link><pubDate>Sat, 15 Aug 2026 11:52:24 -0500</pubDate><guid>https://tardisgallifrey.codeberg.page/posts/archcomp/</guid><description>&lt;h2 id="before-we-learn-to-program"&gt;Before we learn to program&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;m going to start sharing what I know about writing code and developing software, but first I wish to start with sharing some of what happens under the hood.&lt;/p&gt;
&lt;p&gt;I am kind of pedantic about things like this, but I am a member of the &lt;strong&gt;&amp;ldquo;No Black Boxes&amp;rdquo;&lt;/strong&gt; club. I don&amp;rsquo;t like things to be hidden. I prefer to know exactly what is going on in my equipment, my electronics, and even in my programs. Though, I do realize I don&amp;rsquo;t completely care how a given compiler actually works, just that it does its job.&lt;/p&gt;</description></item></channel></rss>