<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Notes on Artful Bytes</title>
    <link>https://artfulbytes.com/notes/</link>
    <description>Recent content in Notes on Artful Bytes</description>
    <generator>Hugo -- 0.131.0</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://artfulbytes.com/notes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I built a computer (try it online)</title>
      <link>https://artfulbytes.com/notes/i-built-a-computer/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://artfulbytes.com/notes/i-built-a-computer/</guid>
      <description>I promised myself to keep my next video simple.
So I built a computer.
A 6502 and a homemade GPIO peripheral. It&amp;rsquo;s a follow-up to my memory-mapped I/O video, this time showing what happens after we write to memory.
While sanity-checking the boards, I had Claude write a simple terminal program that simulates them on my computer, to compare it with the real thing one clock at a time. Then I got ambitious and asked it to turn that into a web version.</description>
    </item>
    <item>
      <title>Do you need to know assembly?</title>
      <link>https://artfulbytes.com/notes/do-you-need-to-know-assembly/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://artfulbytes.com/notes/do-you-need-to-know-assembly/</guid>
      <description>I rarely write assembly.
Never, really.
The compiler does it better, and writing it is more tedious than hard anyway.
Reading it, on the other hand, is often a good way to understand what&amp;rsquo;s going on.
uint32_t adc_to_mv(uint32_t raw) { uint32_t scaled = raw * 3300; uint32_t mv = scaled / 4096; return mv; } int main(void) { // ... uint32_t raw = adc_read(); uint32_t voltage = adc_to_mv(raw); // ... } This code turns a raw reading into millivolts.</description>
    </item>
    <item>
      <title>Where does the stack come from?</title>
      <link>https://artfulbytes.com/notes/where-does-the-stack-come-from/</link>
      <pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://artfulbytes.com/notes/where-does-the-stack-come-from/</guid>
      <description>Start with the CPU.
It executes instructions. Those instructions work on data: add two numbers, compare them, move them around.
That data has to sit somewhere the CPU can reach fast, because it&amp;rsquo;s working on it all the time. That&amp;rsquo;s what the registers are for.
But the registers are few because fast memory is expensive. A real program has far more values than they can hold. That&amp;rsquo;s okay, the CPU only works on a few of them at a time.</description>
    </item>
    <item>
      <title>A follow-up on the RTOS video</title>
      <link>https://artfulbytes.com/notes/a-follow-up-on-the-rtos-video/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://artfulbytes.com/notes/a-follow-up-on-the-rtos-video/</guid>
      <description>A few points came up in the comments on the RTOS video, so I wanted to follow up on some of them.
Several comments pointed out that an RTOS is overkill for the example I showed, and I agree. I made the example intentionally small to demonstrate the core idea. That&amp;rsquo;s often the hard part of these videos: to explain something cleanly, you often have to simplify and leave a lot of nuance out.</description>
    </item>
    <item>
      <title>Is it the software or the hardware?</title>
      <link>https://artfulbytes.com/notes/is-it-the-software-or-the-hardware/</link>
      <pubDate>Thu, 28 May 2026 00:00:00 +0000</pubDate>
      <guid>https://artfulbytes.com/notes/is-it-the-software-or-the-hardware/</guid>
      <description>Is it the software or the hardware?
A question I ask myself when something stops working.
That&amp;rsquo;s when I thank past me for the feral *git commit -am &amp;ldquo;IT WORKS&amp;rdquo; *I made an hour ago.
Not because restoring to that state always works. The hardware can be the real problem. But it often helps me rule out the software.
Sometimes I forget, usually when I&amp;rsquo;m deep into something, tired, just gonna try this one more thing.</description>
    </item>
    <item>
      <title>What embedded systems are really about</title>
      <link>https://artfulbytes.com/notes/what-embedded-systems-are-really-about/</link>
      <pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://artfulbytes.com/notes/what-embedded-systems-are-really-about/</guid>
      <description>If you look up what an embedded system is, you’ll usually find something like this:
“An embedded system is a computer system with a dedicated function within a larger mechanical or electrical system&amp;hellip;”
In short, a computer with a purpose.
That&amp;rsquo;s vague enough that people end up arguing about what counts.
A digital alarm clock? Sure.
A desktop PC? No.
A smartphone? Don’t get me started.
But arguing about definitions only gets you so far and kind of misses the point.</description>
    </item>
  </channel>
</rss>
