<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Noboru Takahashi on Medium]]></title>
        <description><![CDATA[Stories by Noboru Takahashi on Medium]]></description>
        <link>https://medium.com/@noborutakahashi?source=rss-13cd3e66f83e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ugYRjhP2s1TuHk71VGV2mw.png</url>
            <title>Stories by Noboru Takahashi on Medium</title>
            <link>https://medium.com/@noborutakahashi?source=rss-13cd3e66f83e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:46:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@noborutakahashi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Revisiting a 40-Year-Old RTOS: How GitHub and Reddit Helped Shape Its Next Direction]]></title>
            <link>https://medium.com/@noborutakahashi/revisiting-a-40-year-old-rtos-how-github-and-reddit-helped-shape-its-next-direction-7eb06ebbd9d4?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eb06ebbd9d4</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[embedded-systems]]></category>
            <category><![CDATA[raspberry-pi-pico]]></category>
            <category><![CDATA[tor]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 03:23:26 GMT</pubDate>
            <atom:updated>2026-11-14T03:23:26.642Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uevI4tOXtLT1ZZq88GgtPQ.png" /></figure><p><em>From a 1986 RTOS to Karqri on the Raspberry Pi Pico, and the technical discussions that followed.</em></p><p>In 1986, shortly after I started working as a software engineer, I was involved in developing a real-time operating system (RTOS) for the Motorola 68000.</p><p>Almost 40 years later, I found the old source code and documentation and started looking through them again, this time with the help of AI.</p><p>At first, I just wanted to understand the design decisions we had made back then. But after spending some time with the code, I wanted to run it. Then I wanted to try some of the ideas on modern hardware.</p><p>One thing led to another, and I ended up developing a small experimental RTOS called <strong>Karqri</strong>.</p><p>In early November 2026, I published it on GitHub.</p><p>I thought that would be a good place to pause. Instead, posting the project on Reddit gave me quite a few more things to think about.</p><h3>Going Back to 1986</h3><p>The RTOS I worked on in 1986 was designed for embedded systems using the Motorola 68000. We used C and assembly language, working within fairly tight memory and CPU constraints.</p><p>Looking at the code today is a strange experience.</p><p>Some design decisions that seemed perfectly ordinary at the time look quite different when compared with modern RTOS implementations. Others still make sense.</p><p>AI has been useful in this process. I can ask questions about the old code, compare approaches, and work through ideas that would have taken much longer to investigate on my own.</p><p>Eventually, I became more interested in trying the ideas than simply documenting them.</p><p>I wasn’t trying to port the original RTOS unchanged. I wanted to use its design as a starting point for a new experiment.</p><h3>Running Karqri on the Raspberry Pi Pico</h3><p>I started by implementing and testing the basic mechanisms in a POSIX environment, then moved to the Raspberry Pi Pico.</p><p>The Pico uses the RP2040, with dual Cortex-M0+ cores. For now, Karqri uses only one core.</p><p>On the Pico, task switching uses the Cortex-M exception mechanisms, including SVC and PendSV. I now have a demonstration running six tasks with preemptive scheduling.</p><p>That doesn’t mean Karqri is a finished RTOS.</p><p>There are still questions about synchronization, safe shutdown, timing behavior, and other details. I have been concentrating on getting the basic mechanisms working and checking their behavior.</p><p>The source code is available here:</p><p><a href="https://github.com/noboru-takahashi/karqri"><strong>Karqri on GitHub</strong></a></p><p>There are already well-established RTOS projects such as FreeRTOS and Zephyr. I don’t expect Karqri to replace them.</p><p>I published it because I wanted to show what I was experimenting with and see what other developers thought.</p><h3>Posting It on Reddit</h3><p>After publishing the repository, I posted about Karqri in four subreddits:</p><ul><li><a href="https://www.reddit.com/r/osdev/s/pPLAgtDGbb">r/osdev</a></li><li><a href="https://www.reddit.com/r/embedded/s/mY3kWkcJHo">r/embedded</a></li><li><a href="https://www.reddit.com/r/raspberrypipico/s/LPPHotqjgP">r/raspberrypipico</a></li><li><a href="https://www.reddit.com/r/retrocomputing/s/6SZogjkjhQ">r/retrocomputing</a></li></ul><p>The reactions were quite different.</p><p>Some posts attracted little discussion. The r/raspberrypipico post received friendly responses and practical questions about the hardware and scheduler.</p><p>The most detailed technical discussion came from r/embedded, even though the post itself didn’t do particularly well in votes.</p><p>That was interesting. Looking only at the scores, I might have missed the most useful part of the response.</p><h3>A Discussion About Kernel Synchronization</h3><p>One of the people who responded in r/embedded was <strong>ventzl</strong>, who develops an RTOS called CMRX.</p><p>We got into a discussion about protecting shared data structures inside the kernel.</p><p>An RTOS needs to maintain information about tasks that are ready to run, waiting for events, or changing state. An interrupt can occur while the kernel is updating that information.</p><p>The straightforward approach on a single-core system is to disable interrupts while modifying shared state.</p><p>But keeping interrupts disabled for too long affects interrupt latency.</p><p>ventzl described an approach used in CMRX that involves transaction-like operations. Much of the work can be done without holding a long critical section, while the final update is committed within a short protected interval.</p><p>If another operation has changed the relevant state, the transaction can detect the conflict and retry.</p><p>One detail I found particularly interesting was the distinction between making an individual operation atomic and maintaining a consistent view of an entire data structure.</p><p>Those are not necessarily the same problem.</p><p>We also discussed how the assumptions change when moving from single-core to multicore systems. Disabling interrupts on one core does not prevent another core from accessing the same memory.</p><p>I’m not planning to introduce the CMRX approach directly into Karqri at this point. I still want to establish a reliable single-core implementation first.</p><p>But it was useful to hear how someone developing another RTOS had approached the same class of problems.</p><h3>Recording What the RTOS Is Doing</h3><p>Another discussion concerned execution tracing.</p><p>One suggestion was to record events such as task switches, notifications, wakeups, and their causes in a RAM ring buffer, with timestamps.</p><p>The records could then be exported over UART and displayed as a timeline on a PC.</p><p>There was also a suggestion to measure context-switch timing and examine the effects of critical sections.</p><p>ventzl described the tracing mechanism used in CMRX. It stores fixed-size event records in a ring buffer in RAM. When execution stops at a breakpoint or after a crash, the debugger can retrieve the recent history.</p><p>We also talked about hardware tracing features available on some ARM Cortex-M processors, although their availability depends on the particular processor and development hardware.</p><p>For the RP2040, I’m looking at software-based trace collection first.</p><p>What made this discussion especially interesting was that I had a somewhat different reason for wanting traces.</p><p>For debugging, the usual goal is to identify exactly what happened before a failure.</p><p>I also want to observe the behavior of a system that is working normally.</p><p>Years ago, I heard from people building their own CPUs that they could get a sense of what their machines were doing from blinking LEDs or even radio interference.</p><p>They weren’t necessarily decoding individual instructions from those signals. They had become familiar with the patterns and rhythms of their machines.</p><p>I wonder whether something similar could be done with RTOS execution traces.</p><p>That’s still an idea rather than a working feature, but the discussion gave me several practical starting points for collecting the data.</p><h3>What About Real-Time Deadlines?</h3><p>In r/raspberrypipico, someone asked about my scheduler and how it enforced timing windows.</p><p>I wasn’t sure whether the question referred to time slices or task deadlines, so I asked for clarification.</p><p>The follow-up question was more specific: how does the scheduler guarantee that deadlines won’t be missed, and how do tasks communicate their deadlines?</p><p>The answer is that Karqri doesn’t currently do either of those things.</p><p>It supports preemptive task switching, but it doesn’t have deadline-aware scheduling or a mechanism for tasks to declare deadline requirements.</p><p>I haven’t implemented EDF scheduling or performed formal schedulability analysis.</p><p>Those are important distinctions. Being able to switch tasks preemptively doesn’t, by itself, guarantee that a real-time deadline will be met.</p><p>I explained that I was still working on the basic scheduler and context-switching mechanisms. The person who asked seemed satisfied with that answer and encouraged me to continue.</p><p>It was a useful question because it forced me to describe the current scope of the project more precisely.</p><h3>Why Only the RP2040?</h3><p>Another question was whether Karqri works on the RP2350 or RP2354.</p><p>Not yet.</p><p>I’m deliberately limiting the hardware target to the RP2040 for now.</p><p>Supporting another processor would mean more implementation work and more testing. At this stage, I’d rather keep the platform fixed and concentrate on the experiments.</p><p>I may consider other processors later, but I don’t have a plan for that yet.</p><p>It’s a small decision, but an important one for keeping the project manageable.</p><h3>What Is the Point of Another RTOS?</h3><p>Someone else asked a very reasonable question: what is the purpose of the project, and where is it supposed to lead?</p><p>I didn’t have a particularly clear answer when I started.</p><p>I was examining a 40-year-old RTOS. Then I wanted to make some of its ideas work again. Then I started implementing a new system on the Pico.</p><p>Building another RTOS was not really the original objective.</p><p>More recently, I’ve become interested in observing RTOS execution in a different way.</p><p>There are already trace analysis tools, including Perfetto and Eclipse Trace Compass. I plan to try those first.</p><p>But I’m also curious about visual representations that might make task activity, interrupts, and event timing easier to recognize without examining every event individually.</p><p>I haven’t started the main experiments yet, so there’s not much more to report at this point.</p><p>I’ll write about that separately once I have something running.</p><h3>Different Communities, Different Responses</h3><p>Posting the same project in several communities was an experiment in itself.</p><p>I had expected r/osdev to be a natural place to discuss a small RTOS. It was certainly relevant, but the post didn’t lead to much conversation.</p><p>In r/embedded, I received detailed comments about synchronization and tracing from people with practical RTOS development experience.</p><p>In r/raspberrypipico, the questions were more about what the implementation could actually do on the hardware.</p><p>I wouldn’t draw broad conclusions about the communities from a single set of posts.</p><p>Still, the differences were noticeable.</p><p>The vote counts didn’t tell me very much about the value of the feedback. A detailed exchange with one experienced developer was worth more to me than a high score with no discussion.</p><p>I also found that answering questions helped me clarify my own priorities.</p><p>Some features are missing because I haven’t implemented them yet. Others are deliberately outside the current scope. Explaining that distinction to someone else made me think more carefully about it.</p><h3>Publishing Was the Beginning</h3><p>Most of the development work up to this point had involved a continuing dialogue with AI.</p><p>I would discuss an idea, work through an implementation, test it, examine what went wrong, and try again.</p><p>That process helped me get from examining an old RTOS to running a new experimental one on the Pico.</p><p>Publishing the source code brought other people into the discussion.</p><p>They asked about synchronization, deadline guarantees, hardware support, and tracing. Some of those questions exposed work I still need to do. Others gave me ideas for experiments I hadn’t fully considered.</p><p>I still don’t know exactly what Karqri will become.</p><p>For now, I’ll keep working on the single-core implementation and begin experimenting with trace collection and visualization.</p><p>I started this project by looking back at something I worked on in 1986.</p><p>Forty years later, it has turned into something quite different.</p><p><strong>Publishing the code on GitHub wasn’t the finish line. It was the starting point.</strong></p><h3>Related Reading<br><a href="https://medium.com/@noborutakahashi/series-1980s-real-time-os-fd24fc389274?sharedUserId=noborutakahashi">1980s Real-Time-OS — Article Series</a></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb06ebbd9d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My AI Money Tree Might Be Sprouting]]></title>
            <link>https://medium.com/@noborutakahashi/my-ai-money-tree-might-be-sprouting-d5dfcf1d9857?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5dfcf1d9857</guid>
            <category><![CDATA[passive-income]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[indie-hacking]]></category>
            <category><![CDATA[side-hustle]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 03:57:49 GMT</pubDate>
            <atom:updated>2026-11-07T04:01:41.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MBMaHBOF4SrYQinDI8Bnjw.png" /></figure><p><em>I left a tiny open-source utility alone for a while. When I checked again, the numbers were more interesting than I expected.</em></p><p>A few weeks ago, I wrote an article called <a href="https://medium.com/@noborutakahashi/i-planted-an-ai-money-tree-69f580f58a0e">I Planted an AI Money Tree</a>.</p><p>The idea was simple.</p><p>What if I could use AI to create small software tools, release them on the internet, and let them grow with very little ongoing effort?</p><p>I’m not trying to build a startup or become rich overnight.</p><p>I’d be perfectly happy with a few tiny money trees that occasionally produce enough for a cup of coffee or a drink with a friend.</p><p>The first tree I planted was a Windows utility called OfflineHEIC.</p><p>After making a few improvements to its website, I left it alone again.</p><p>Recently, I decided to check on it.</p><h3>Checking on My First Tree</h3><p><a href="https://noboru-takahashi.github.io/OfflineHEIC/">OfflineHEIC</a> is a small Windows application that converts HEIC images to JPEG or PNG without uploading them anywhere.</p><p>I built it with AI assistance, released it as open-source software, and created a simple landing page using GitHub Pages.</p><p>I also registered the website with Google Search Console, made a few SEO improvements, and installed Google Analytics.</p><p>Then I stopped working on it.</p><p>That was intentional.</p><p>The whole point of my AI money tree experiment is to find out whether small products can attract users without requiring constant attention.</p><p>If I have to spend hours promoting a tool every day, it starts looking less like a money tree and more like another job.</p><h3>Seventy-One Visitors</h3><p>When I opened Google Analytics in early November, I found that the website had attracted 71 active users over the previous 30 days.</p><p>Not exactly a traffic explosion.</p><p>But it was more activity than I had seen before.</p><p>During an earlier check, I had also noticed something interesting about the traffic sources.</p><p>Some visitors had arrived through Google and Bing, as expected.</p><p>But a few had come from ChatGPT and Gemini.</p><p>I had been experimenting with traditional search engine optimization, yet AI assistants were apparently another route by which people could reach the site.</p><p>I don’t know what questions those visitors asked, or whether the AI assistants explicitly recommended my application.</p><p>Still, it was an interesting observation.</p><p>The tree wasn’t growing very quickly, but something seemed to be happening.</p><h3>Wait. How Many Downloads?</h3><p>While looking at Google Analytics, another question occurred to me.</p><p>How many people had actually downloaded the software?</p><p>The landing page was only part of the story. The application itself was distributed through GitHub Releases.</p><p>I discovered that GitHub’s API could tell me how many times the release file had been downloaded.</p><p>So I ran a PowerShell command:</p><pre>(Invoke-RestMethod https://api.github.com/repos/noboru-takahashi/OfflineHEIC/releases/latest).assets |<br>Select-Object name, download_count</pre><p>The result was:</p><p><strong>OfflineHEIC-v0.1.0.zip — 160 downloads</strong></p><p>Wait, 160?</p><p>That was more than I expected.</p><p>From the Google Analytics numbers, I had assumed that almost nobody was interested in the application.</p><p>But the download counter suggested there was more activity than I had realized.</p><p>Of course, 160 downloads doesn’t mean 160 people are using OfflineHEIC.</p><p>Some may be repeat downloads. Some may be my own tests. Automated downloads may also be included.</p><p>And I have no way of knowing how many people actually ran the application after downloading it.</p><p>Even so, the number surprised me.</p><h3>Two Different Windows Into the Same Experiment</h3><p>At first, I wondered why the download count was larger than the website traffic.</p><p>Then I realized I was comparing two different things.</p><p>Google Analytics measures activity on my GitHub Pages website.</p><p>GitHub Releases counts downloads of the ZIP file.</p><p>Someone can discover OfflineHEIC through its GitHub repository and download it without ever visiting the landing page.</p><p>And the two numbers cover different periods.</p><p>The 71 active users were counted over the previous 30 days. The 160 downloads were cumulative.</p><p>So there is no real contradiction.</p><p>But this raised a more interesting question.</p><p><strong>Where are those downloads coming from?</strong></p><p>Google Search?</p><p>GitHub search?</p><p>An AI assistant?</p><p>A link someone shared somewhere?</p><p>I don’t know.</p><p>And GitHub’s cumulative download counter doesn’t tell me when those downloads happened.</p><p>I had been watching the website, assuming it represented the growth of my little money tree.</p><p>Apparently, I had only been looking at one part of it.</p><h3>Is That a Tiny Sprout?</h3><p>So, has my first AI money tree started growing?</p><p>Maybe a little.</p><p>It has still earned exactly zero dollars.</p><p>In fact, I haven’t even added a donation button or any other way to make money from it.</p><p>That part hasn’t changed since my previous article.</p><p>But I wasn’t trying to monetize it immediately.</p><p>First, I wanted to see whether a small application built with AI assistance could find users without much promotion or maintenance.</p><p>The download count doesn’t prove that people are using it successfully.</p><p>But it does suggest that the release file is being discovered and downloaded.</p><p>That’s a small but encouraging sign.</p><p>Not a tree yet.</p><p>Perhaps just a tiny sprout emerging from the soil.</p><h3>Maybe It’s Time to Water It</h3><p>For now, I’ve decided to start recording the download count regularly.</p><p>Today’s baseline is 160 downloads.</p><p>If I check again next month, I’ll at least know how many additional downloads occurred during that period.</p><p>I’m also thinking about asking for advice on Reddit.</p><p>How do other independent developers get people to discover their small open-source tools?</p><p>How do they measure interest when their software is distributed through GitHub?</p><p>And what kinds of promotion are actually worth the effort?</p><p>I might try a few suggestions and see what happens.</p><p>But I don’t want to turn this into a full-time marketing exercise.</p><p>The original idea was to create several small products with AI, give them a chance to grow, and keep the ongoing work to a minimum.</p><p>So perhaps I’ll water this one a little, then leave it alone again.</p><p>My first AI money tree hasn’t produced any money.</p><p>But for the first time, I think I might be seeing a small green shoot.</p><p>And I’m curious to see what happens next.</p><p><strong>Previously:</strong> <a href="https://medium.com/@noborutakahashi/i-planted-an-ai-money-tree-69f580f58a0e">I Planted an AI Money Tree</a></p><p><a href="https://medium.com/@noborutakahashi/series-thinking-with-ai-fe99775685a1?postPublishedType=repub"><strong>Series: Thinking with AI</strong></a></p><p><strong>The experiment:</strong> <a href="https://noboru-takahashi.github.io/OfflineHEIC/">OfflineHEIC — Free Offline HEIC Converter for Windows</a></p><p><strong>Source code:</strong> <a href="https://github.com/noboru-takahashi/OfflineHEIC">OfflineHEIC on GitHub</a></p><p><em>This is an ongoing experiment in using AI as a thinking and building partner, rather than a story about making money with AI.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5dfcf1d9857" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Planted an AI Money Tree]]></title>
            <link>https://medium.com/@noborutakahashi/i-planted-an-ai-money-tree-69f580f58a0e?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/69f580f58a0e</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[personal-project]]></category>
            <category><![CDATA[indie-hacking]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[side-hustle]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 12:57:35 GMT</pubDate>
            <atom:updated>2026-10-14T12:57:35.682Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxKVc703WKBgrQG43AaFsA.png" /></figure><p>I’ve always wanted a money tree.</p><p>Not necessarily one that makes me rich. Just a small tree that produces a little money now and then.</p><p>Enough for a cup of coffee. Maybe dinner. Or a drink with a friend.</p><p>And preferably, without having to work too hard for it.</p><p>Of course, that’s the difficult part.</p><h3>Money Trees Have Been Around for a Long Time</h3><p>In the real world, we already have things that resemble money trees.</p><p>Rental properties generate rent. Stocks pay dividends. Books can earn royalties long after they’re written.</p><p>But there’s a catch.</p><p>You need money to buy a property or stocks. Writing a book takes considerable time and effort. And even after you’ve created something, keeping it profitable may require ongoing work.</p><p>A money tree isn’t free. You have to plant it, and sometimes you have to keep watering it.</p><p>But what if AI could make planting one much easier?</p><p>I’m not talking about asking AI to generate a million-dollar business idea.</p><p>I’m thinking much smaller.</p><p>What if I could use AI to find a tiny problem, build something that solves it, and put it on the internet with relatively little effort?</p><p>Then leave it there and see what happens.</p><p>Maybe I could plant several such trees.</p><p>Most might never grow. But perhaps one or two would eventually produce something.</p><p>That’s the experiment I want to try.</p><h3>Actually, I’ve Already Planted One</h3><p>A few months ago, I made a small Windows utility called <strong>OfflineHEIC</strong>.</p><p>It converts HEIC image files to JPEG files entirely on your computer.</p><p>There are already plenty of online converters, of course. But uploading images to a website isn’t always an option, especially when you’re working with company files or private photographs.</p><p>The idea came from a real problem someone mentioned to me.</p><p>With AI helping me write and troubleshoot the code, I was able to turn that small problem into a working application.</p><p>I released it for free and made the source code available.</p><p><a href="https://noboru-takahashi.github.io/OfflineHEIC/">OfflineHEIC — Free Offline HEIC to JPEG Converter</a></p><p>Originally, I called it SafeHEIC. Then I discovered that another project was already using that name, complete with its own website.</p><p>So I renamed mine OfflineHEIC.</p><p>Even naming a tiny money tree turned out to require a little maintenance.</p><h3>But the Tree Wasn’t Growing</h3><p>After releasing OfflineHEIC, I more or less forgot about it.</p><p>Months passed.</p><p>When I finally checked how things were going, I discovered that hardly anyone was visiting the website.</p><p>I’d made something and put it online, but that didn’t mean anyone would find it.</p><p>Which, in retrospect, should have been obvious.</p><p>So I made a few improvements to the website, worked on its search engine visibility, and added Google Analytics.</p><p>Then I left it alone again.</p><p>When I checked recently, there seemed to be a little more traffic than before.</p><p>Not much. And it’s far too early to tell whether actual users are finding the application useful.</p><p>Still, the graph wasn’t completely flat anymore.</p><p>That’s something.</p><p>I was thinking about all this while waiting for a table at a restaurant.</p><p>Apparently, waiting for dinner is a perfectly good time to start thinking about growing money trees.</p><h3>There’s Another Small Problem</h3><p>OfflineHEIC doesn’t have any way to make money.</p><p>No price tag. No donation button. No paid version.</p><p>Nothing.</p><p>So even if someone downloads it and finds it useful, the tree currently has no mechanism for producing a single coin.</p><p>But I’m not particularly worried about that yet.</p><p>First, I want to know whether anyone actually needs it.</p><p>If nobody uses the application, adding a payment mechanism won’t solve the real problem.</p><p>For now, I’m more interested in whether this little tree can attract visitors and users without constant attention.</p><h3>The Kind of Tree I Want to Grow</h3><p>There are countless books and articles about starting a side hustle with little or no money.</p><p>But many of those ideas require a great deal of personal effort.</p><p>You may not need much capital, but you still have to keep working.</p><p>That’s not quite the money tree I’m imagining.</p><p>I’m interested in something that requires relatively little effort to create and, ideally, very little effort to maintain.</p><p>AI changes the equation because it can help with research, programming, writing, design, and troubleshooting.</p><p>Things that once required considerable time — or several different skills — have become much easier to attempt.</p><p>Of course, AI doesn’t magically create customers.</p><p>And making something easy to build doesn’t make it valuable.</p><p>That may turn out to be the most important lesson of this experiment.</p><h3>Looking for the Next Seeds</h3><p>I’ve also started looking through books about money trees, investing, and small businesses.</p><p>One interesting discovery is just how often the phrase <em>money tree</em> appears in book titles.</p><p>Some books talk about finding a money tree. Others tell you to grow one. Some seem to be about investing, while others are about starting a business.</p><p>The phrase even appears in old folk tales.</p><p>People have apparently been dreaming about money growing on trees for a very long time.</p><p>I’m curious about what happens when that old dream meets today’s AI tools.</p><p>So I’ll keep reading, experimenting, and occasionally planting another seed.</p><p>I don’t have a business plan for this series. I don’t even know whether the first tree will survive.</p><p>And I certainly don’t have any success stories to sell.</p><h3>Will My Money Tree Ever Bear Fruit?</h3><p>I have no idea.</p><p>So far, my first tree has produced exactly zero money.</p><p>It has, however, given me quite a few things to think and write about.</p><p>That’s not quite the return I was hoping for, but it’s a start.</p><p>Maybe the next tree will do better.</p><p>Or maybe I’ll end up with a whole collection of tiny, unproductive trees.</p><p>Either way, I think it’ll be interesting to find out.</p><p><em>This is an experiment in using AI as a thinking and building partner. For more about that approach, see my </em><a href="https://medium.com/@noborutakahashi/series-thinking-with-ai-fe99775685a1?sharedUserId=noborutakahashi"><strong><em>Thinking with AI series.</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69f580f58a0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Series: Thinking with AI]]></title>
            <link>https://medium.com/@noborutakahashi/series-thinking-with-ai-fe99775685a1?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe99775685a1</guid>
            <category><![CDATA[artficial-intelligence]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 12:44:15 GMT</pubDate>
            <atom:updated>2026-11-07T04:00:26.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTKKvcDnBA__XpboqYj74A.png" /></figure><ul><li><a href="https://medium.com/@noborutakahashi/i-planted-an-ai-money-tree-69f580f58a0e?sharedUserId=noborutakahashi"><strong>I Planted an AI Money Tree</strong></a></li><li><a href="https://medium.com/@noborutakahashi/my-ai-money-tree-might-be-sprouting-d5dfcf1d9857"><strong>My AI Money Tree Might Be Sprouting</strong></a></li><li><a href="https://medium.com/@noborutakahashi/i-asked-ai-to-rate-how-i-use-ai-the-score-turned-out-to-be-the-least-interesting-part-7661d6e4dd0e?sharedUserId=noborutakahashi"><strong>I Asked AI to Rate How I Use AI. The Score Turned Out to Be the Least Interesting Part.</strong></a></li><li><a href="https://medium.com/@noborutakahashi/some-of-my-best-ideas-happen-after-i-close-chatgpt-13fa6aebeb60?sharedUserId=noborutakahashi"><strong>Some of My Best Ideas Happen After I Close ChatGPT</strong></a></li><li><a href="https://medium.com/@noborutakahashi/a-little-girl-an-instant-team-and-an-unexpected-lesson-about-ai-4651bb635a14?sharedUserId=noborutakahashi"><strong>A Little Girl, an Instant Team, and an Unexpected Lesson About AI</strong></a></li><li><a href="https://medium.com/@noborutakahashi/why-generative-ai-trade-shows-feel-so-different-f471748b5a38?sharedUserId=noborutakahashi"><strong>AI Started With Consumers Before Enterprises — And That Changed Everything</strong></a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe99775685a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Revisited My 40-Year-Old RTOS — and Met Someone Who Used VRTX in 1982]]></title>
            <link>https://medium.com/@noborutakahashi/i-revisited-my-40-year-old-rtos-and-met-someone-who-used-vrtx-in-1982-615473044a50?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/615473044a50</guid>
            <category><![CDATA[computer-history]]></category>
            <category><![CDATA[embedded-systems]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[operating-systems]]></category>
            <category><![CDATA[retrocomputing]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 06:49:46 GMT</pubDate>
            <atom:updated>2026-10-10T06:56:41.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RbFUf30JgpcT62FcYp5bvQ.png" /></figure><p><em>Reconstructing a real-time operating system I wrote in 1986 led to a scheduling mystery, an unexpected discovery in my own code, and a conversation across four decades.</em></p><p>In 1986, I developed a real-time operating system called CHARM-II for the Motorola 68000.</p><p>Forty years later, I’m revisiting that system and rebuilding it for modern hardware.</p><p>This isn’t simply a matter of recompiling old source code. I’m examining the original implementation, trying to understand the design decisions I made at the time, and using what I learn to develop a modern RTOS called Karqri.</p><p>During this work, I ran into a question about how tasks of equal priority should be scheduled.</p><p>Looking into it, I discovered that my understanding of a commercial RTOS I had used as a reference in 1986 was not entirely accurate.</p><p>I also discovered that the RTOS itself had changed its scheduling behavior during the 1980s.</p><p>Why had it changed?</p><p>I asked the question on Reddit, expecting perhaps a few technical explanations.</p><p>Instead, the discussion led to several unexpected discoveries — including a conversation with someone who had been using that RTOS as early as 1982.</p><p>Here’s what happened.</p><h3>A Scheduling Decision Hidden in My 1986 RTOS</h3><p>CHARM-II was a small real-time operating system I developed in 1986 for Motorola 68000-based embedded systems.</p><p>At the time, commercial RTOS products such as VRTX and pSOS already existed. I consulted their documentation while designing CHARM-II.</p><p>I wasn’t using VRTX itself, nor was I trying to build a compatible implementation. I was designing and implementing the functionality I needed for my own system.</p><p>One fundamental responsibility of an RTOS is deciding which task should run when multiple tasks are ready.</p><p>When their priorities differ, the scheduler normally selects the highest-priority task.</p><p>But what happens when several ready tasks have the same priority?</p><p>There are several possible approaches:</p><ul><li><strong>FIFO (First In, First Out):</strong> Tasks that became ready earlier are scheduled first.</li><li><strong>LIFO (Last In, First Out):</strong> Tasks that became ready more recently are scheduled first.</li><li><strong>Round-robin:</strong> Tasks of equal priority take turns, typically using time slices.</li></ul><p>Actual RTOS scheduling behavior can be more complicated than these simple categories suggest.</p><p>When I examined the original CHARM-II source code, I found that a newly ready task was inserted ahead of existing tasks with the same priority.</p><p>In other words, the ready queue generally used a <em>newest-first</em> insertion rule.</p><p>However, CHARM-II also implemented time-slice rotation, so it wasn’t strictly LIFO in every situation.</p><p>Still, my basic design assumption in 1986 appears to have been that equal-priority scheduling should behave in a LIFO-like manner.</p><p>Why had I chosen that approach?</p><p>The answer seemed to lie in the VRTX documentation I had consulted.</p><h3>VRTX Behaved Differently in 1984 and 1987</h3><p>The 1984 <em>VRTX User’s Guide</em> describes a rule in which a newly ready task is inserted ahead of existing ready tasks with the same priority.</p><p>That closely resembles the insertion behavior in CHARM-II.</p><p>But the 1987 <em>VRTX32 User’s Guide</em> describes FIFO ordering among ready tasks of equal priority.</p><p>At least according to these two documents, the ready-queue ordering rules were different.</p><p>The development of CHARM-II in 1986 fell right around this period of change.</p><p>That raised an intriguing question:</p><p><strong>Why did VRTX change its equal-priority ready-queue ordering from newest-first to FIFO?</strong></p><p>FIFO seems more straightforward from the perspective of fairness.</p><p>But if FIFO was preferable, why hadn’t the original designers used it from the beginning?</p><p>Was there a performance advantage to newest-first ordering?</p><p>Had the developers discovered a problem that motivated the change?</p><p>I wanted to know what the original VRTX developers had been thinking.</p><h3>Asking Three Reddit Communities</h3><p>I could establish that the documented behavior had changed, but the manuals alone didn’t explain why.</p><p>So on September 26, 2026, I posted questions in three Reddit communities:</p><ul><li><a href="https://www.reddit.com/r/osdev/s/h6PG9bZO7a">r/osdev: Why did VRTX change equal-priority scheduling from newest-first to FIFO?</a></li><li><a href="https://www.reddit.com/r/embedded/s/gMr2klUiCY">r/embedded: Did anyone here use VRTX in the 1980s? Why did equal-priority scheduling change to FIFO?</a></li><li><a href="https://www.reddit.com/r/retrocomputing/s/vnT1JWZRtQ">r/retrocomputing: I found out that VRTX changed its scheduling behavior just after I used it as a reference in 1986 — does anyone know why?</a></li></ul><p>I approached the same question from slightly different angles.</p><p>In r/osdev, I focused on operating-system design. In r/embedded, I was interested in practical embedded-system experience. In r/retrocomputing, I hoped to find people familiar with the hardware, software, and documentation of that era.</p><p>About two weeks later, the three posts had accumulated roughly 20,000 views in total.</p><p>Of course, views aren’t unique readers, and some people may have seen more than one post.</p><p>Still, I hadn’t expected such a specialized question about a 1980s RTOS to attract that much attention.</p><p>More importantly, the comments brought several useful technical perspectives.</p><h3>The Trade-Off Between Newest-First and FIFO</h3><p>One recurring topic was fairness and starvation.</p><p>Suppose tasks A and B are ready at the same priority.</p><p>Then task C becomes ready.</p><p>With newest-first insertion, C goes ahead of A and B.</p><p>If tasks repeatedly wake up, perform short operations, block, and become ready again, they may repeatedly move ahead of tasks that have already been waiting.</p><p>Under certain workloads, the older ready tasks may receive very little CPU time.</p><p>This is a form of <em>starvation</em>.</p><p>FIFO ordering reduces that particular risk by placing newly ready tasks behind those already waiting at the same priority.</p><p>But newest-first insertion also has potential advantages.</p><p>For example, a task that has just been awakened by an event may benefit from being scheduled quickly, reducing its response latency.</p><p>There are also implementation trade-offs to consider.</p><p>So the question isn’t simply whether LIFO is bad and FIFO is good.</p><p>It depends on what behavior the system is designed to optimize.</p><h3>Insights from Someone Who Had Built a Scheduler</h3><p>One particularly interesting comment came from someone who had implemented equal-priority round-robin scheduling in an RTOS.</p><p>The discussion went beyond the cost of inserting tasks into a ready queue.</p><p>It touched on context-switch overhead, cache behavior, task execution patterns, and an approach described as <em>semi-LIFO</em>.</p><p>This was a useful reminder that scheduling isn’t merely about arranging items in a queue.</p><p>The overall behavior depends on how frequently tasks wake up, how long they execute, why they block, and how they interact with other tasks.</p><p>Even the small ready-queue implementation I wrote 40 years ago contained more design implications than I had appreciated at the time.</p><h3>Early VRTX Wasn’t Simply LIFO</h3><p>Another important discovery emerged from the discussion.</p><p>A commenter who examined the early VRTX documentation pointed out that its ready-queue behavior wasn’t as simple as calling it LIFO.</p><p>Yes, a newly ready task could be inserted ahead of existing tasks of the same priority.</p><p>But when a time slice expired, the running task could be rotated toward the end of its equal-priority group.</p><p>Other task-state transitions also affected ready-queue ordering.</p><p>To understand the scheduler accurately, you needed to consider <strong>how a task entered or re-entered the ready state</strong>, not merely whether the queue was labeled FIFO or LIFO.</p><p>Another commenter brought up the subtleties of POSIX SCHED_FIFO.</p><p>A task preempted by a higher-priority task does not necessarily lose its position relative to equal-priority tasks. Blocking and waking, or voluntarily yielding, can have different consequences.</p><p>This didn’t explain the historical VRTX change, but it reinforced an important point: the detailed rules matter.</p><p>And it made me reconsider my own implementation.</p><h3>I Had Oversimplified VRTX in 1986</h3><p>The equal-priority scheduling behavior in CHARM-II was influenced by the VRTX documentation.</p><p>But I now realize that I had interpreted VRTX as essentially using a simple newest-first, LIFO-like scheme.</p><p>I then implemented my own simplified version of that interpretation.</p><p>Comparing the historical documentation with my source code 40 years later made it clear that I hadn’t reproduced all the nuances of VRTX’s behavior.</p><p>Of course, CHARM-II was never intended to be VRTX-compatible, so a difference in behavior was not inherently a defect.</p><p>What interests me is that I apparently hadn’t fully understood the distinction at the time.</p><p>And there is another curious point.</p><p><strong>I don’t remember that scheduling choice causing serious problems in the actual applications.</strong></p><p>Why not?</p><h3>Why Didn’t It Cause Problems?</h3><p>This is something I’ve been thinking about while revisiting the development environment of 1986.</p><p>At the time, I was developing almost the entire application as well as the RTOS myself.</p><p>Today, embedded systems often combine components written by many different developers, including open-source libraries, middleware, and third-party software.</p><p>My development environment in 1986 was very different.</p><p>There was very little third-party code.</p><p>I had written most of the system myself, from the RTOS to the application tasks.</p><p>As a result, I understood what individual tasks were doing, when they would become ready, and how they interacted.</p><p>If the scheduler had an unusual characteristic, I could design the application around it.</p><p>If tasks of equal priority behaved inconveniently, I could change their priorities, adjust task boundaries, or reconsider how events were used.</p><p>I can’t prove that this explains why I encountered no serious problems. It was 40 years ago, and I may have forgotten some difficulties.</p><p>But looking back, I suspect the development environment was an important factor.</p><p><strong>Rather than treating the RTOS as a general-purpose execution environment for independently developed components, I could design the RTOS and application as one integrated system.</strong></p><p>At least, that was true of the systems I was building.</p><p>This distinction also matters when considering what should be explicitly specified in a modern RTOS.</p><h3>Then Someone Who Had Used VRTX in 1982 Appeared</h3><p>The most unexpected part of the entire discussion happened in r/retrocomputing.</p><p>A commenter described using VRTX around 1982.</p><p>Not just any VRTX installation, either. They had worked with some very early VRTX ROMs, reportedly bearing serial numbers 1001 through 1009.</p><p>Their system used a Motorola MVME board with a 68000 processor and was developed for engine and dynamometer data acquisition and control.</p><p>They described a system combining tasks for periodic data acquisition, control calculations, file management, and display updates.</p><p>They also recalled hardware such as a custom VME counter/timer board, a 12-bit ADC, and an Iomega Bernoulli disk.</p><p>There were even memories of speaking with members of the VRTX development team by telephone.</p><p>These were firsthand details from an actual embedded development environment more than four decades ago.</p><p>And one detail immediately caught my attention.</p><p>I had also used a Motorola MVME 68000 board for a later application built with CHARM-II.</p><p>Here I was, in 2026, talking with someone who had developed a different system using similar hardware in the early 1980s.</p><p>That was quite an unexpected connection.</p><h3>They Hadn’t Paid Much Attention to LIFO Versus FIFO Either</h3><p>Another interesting detail was that this early VRTX user hadn’t paid particular attention to the LIFO-versus-FIFO distinction.</p><p>Their system had worked well for its intended purpose.</p><p>That doesn’t explain why VRTX eventually changed its scheduling behavior.</p><p>But it does tell us that, for at least one early user, the distinction hadn’t been a significant concern.</p><p>Meanwhile, I had developed CHARM-II in 1986 using a simplified interpretation of VRTX and didn’t remember serious practical problems either.</p><p>Our systems and design decisions were not necessarily the same.</p><p>Still, comparing those two experiences gave me a glimpse of what embedded development was like during that period.</p><h3>I Chose FIFO for Modern Karqri</h3><p>So what did I decide for Karqri?</p><p>I chose FIFO ordering among ready tasks of equal priority.</p><p>Karqri isn’t intended to be merely an exact reproduction of CHARM-II.</p><p>My approach is to understand and validate the original implementation first, then use that knowledge to design a modern RTOS.</p><p>That means I don’t need to preserve every historical behavior simply because it existed in the 1986 code — or in the VRTX documentation I consulted.</p><p>For the current Karqri design, FIFO offers a simpler and more predictable rule.</p><p>Of course, FIFO alone doesn’t solve every scheduling problem. Priority assignment, execution time, blocking behavior, and task interactions still matter.</p><p>But it is the design choice I’ve made for now.</p><h3>Karqri Is Already Running on Raspberry Pi Pico</h3><p>Karqri has now reached the point where a minimal configuration runs on a Raspberry Pi Pico.</p><p>I’m developing it for both POSIX environments and the Pico, so the project has moved beyond simply studying historical source code.</p><p>I intend to publish the source code on GitHub, but I’m currently reviewing it before release.</p><p>Because the project began with a 40-year-old implementation, I want to distinguish clearly between the restored historical behavior and the parts redesigned for the modern version.</p><p>I’m also reviewing the implementation, specifications, and documentation.</p><p>So I’m proceeding a little cautiously with the public release.</p><p>I’ll share more once it’s ready.</p><h3>So Why Did VRTX Switch to FIFO?</h3><p>After all this investigation, the original question remains unanswered.</p><p>The 1984 VRTX documentation describes newest-first insertion among equal-priority ready tasks.</p><p>The 1987 VRTX32 documentation describes FIFO ordering.</p><p>There are plausible technical explanations involving fairness, starvation, latency, and implementation trade-offs.</p><p>But I still haven’t found documentation or firsthand testimony establishing why the VRTX developers actually made the change.</p><p>For now, the historically accurate answer is simply that I don’t know.</p><p>Yet the investigation was far from pointless.</p><p>It began as a practical design question about how to implement the Karqri scheduler.</p><p>I could have chosen FIFO and moved on.</p><p>Instead, I examined my 1986 source code, revisited the VRTX manuals, and asked other developers about their experiences.</p><p>That process revealed something about what I had understood — and misunderstood — 40 years ago.</p><p>It also made me reconsider the development environment in which CHARM-II had been created.</p><p>And, unexpectedly, it led to a conversation with someone who had been using VRTX before I even wrote CHARM-II.</p><p><strong>The original 40-year-old mystery remains unsolved. But I now see both the old system and my own work very differently.</strong></p><p>Apparently, bringing old source code back to life can lead to more than just a working program.</p><h4>Related Reading<br><a href="https://medium.com/@noborutakahashi/series-1980s-real-time-os-fd24fc389274?sharedUserId=noborutakahashi"><strong>1980s Real-Time-OS — Article Series</strong></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=615473044a50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Asked AI to Rate How I Use AI. The Score Turned Out to Be the Least Interesting Part.]]></title>
            <link>https://medium.com/@noborutakahashi/i-asked-ai-to-rate-how-i-use-ai-the-score-turned-out-to-be-the-least-interesting-part-7661d6e4dd0e?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/7661d6e4dd0e</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[human-ai-collaboration]]></category>
            <category><![CDATA[microsoft-copilot]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 02:34:34 GMT</pubDate>
            <atom:updated>2026-10-14T13:16:57.309Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F5NBDVBXEIcKrS8Kf28GfQ.png" /></figure><p>A few weeks ago, I asked ChatGPT a slightly silly question.</p><blockquote><em>Based on what you know about how I actually use ChatGPT, if the maximum level of ChatGPT usage is Level 100, what level am I currently at?</em></blockquote><p>It gave me <strong>92/100</strong>.</p><p>I knew, of course, that this wasn’t a real measurement. There is no standardized test for “ChatGPT level,” and 92 doesn’t mean I am objectively in the top 8% of anything.</p><p>Still, I found the idea amusing.</p><p>I use ChatGPT a lot, not only for getting answers or writing text, but for discussing ideas, questioning assumptions, working through technical problems, and sometimes continuing the same line of thought over several days.</p><p>So I wondered what other people’s ChatGPT would say about them.</p><p>I made a post in r/ChatGPT:</p><p><a href="https://www.reddit.com/r/ChatGPT/s/e31xWnG28c?utm_source=chatgpt.com">I asked ChatGPT what level AI user I am. It gave me 92/100. What does yours say?</a></p><p>And then I made a very obvious mistake.</p><h3>I put 92 in the title</h3><p>People started trying the same prompt and posting their scores.</p><p>78 82 88 92 96</p><p>There were some interesting explanations too, but the scores tended to be high.</p><p>At first, that looked interesting in itself.</p><p>Then people started pointing out problems with the experiment.</p><p>One person questioned whether ChatGPT would give anyone a genuinely low score. Others pointed out that changing the framing of the question could change the result. There was also the broader problem of asking an AI to evaluate a person based on what that same AI happened to know about them.</p><p>And then there was the most obvious problem of all.</p><p>I had written <strong>92/100 in the title</strong>.</p><p>Before anyone asked ChatGPT for a number, I had already shown them a very high number.</p><p>Even if ChatGPT itself never saw the Reddit post, the humans participating in the experiment did.</p><p>And there was another possible selection effect. If someone’s ChatGPT gave them 40 or 50, would they be as likely to post it in a thread where the original poster announced a 92?</p><p>I had set out to see what numbers people would get, but I had probably influenced which numbers ended up in the comments.</p><p>The experiment wasn’t useless, though. In fact, the mistake made the next question more interesting.</p><h3>So I tried it again with Copilot</h3><p>I use Microsoft Copilot at work, so I moved the experiment to r/microsoft_365_copilot.</p><p>This time I changed the prompt:</p><blockquote><em>Based on what you know about how I actually use Copilot, if the maximum level of AI usage is Level 100, what level am I currently at?</em></blockquote><blockquote><em>Give me one number, then briefly explain why. Be critical rather than encouraging, and don’t give me credit for things you don’t have evidence that I actually do.</em></blockquote><p>More importantly, I <strong>didn’t tell anyone my score</strong>.</p><p>I asked people to post what their Copilot told them, but kept my own result hidden until the experiment was basically over.</p><p>The scores were much more spread out.</p><p>Among the responses that gave a usable single number, I saw scores ranging from <strong>38 to 90</strong>.</p><p>That looked much healthier than my first experiment.</p><p>But I can’t claim that hiding my score caused the difference.</p><p>This wasn’t a controlled experiment. It was a different community, a different AI product, and a slightly different prompt. People could also see scores that other commenters had already posted.</p><p>So I don’t think the interesting conclusion is “Copilot scores people more accurately” or “ChatGPT is more flattering.”</p><p>Something else caught my attention.</p><h3>The scores were different. The reasons weren’t.</h3><p>A person who got 63 and a person who got 88 might sound very different at first.</p><p>But when I read through Copilot’s explanations, the same general direction kept appearing.</p><p>Basic use was things like asking questions, drafting, summarizing, and getting help with everyday work.</p><p>Then came research, analysis, troubleshooting, reviewing, and using AI as a thinking or design partner.</p><p>Further up the scale, Copilot started looking for something else:</p><p>workflow integration, reusable processes, automation, agents, connections to business systems, and eventually end-to-end processes that could operate with less human intervention.</p><p>This pattern showed up repeatedly.</p><p>One person received 65 even though they used Copilot heavily for troubleshooting, PowerShell, KQL, reports, summaries, email drafting, and operational guidance. Copilot’s reason for not scoring them higher was that much of the work was still “human-driven request/response.”</p><p>Another received 78 despite working with Copilot Studio, Power Automate, SharePoint, Power Platform and custom agents. Again, the distinction was that most of the examples were still “AI-assisted work” rather than “AI-operated work.”</p><p>Others got similar comments about not yet having enough end-to-end automation, autonomous workflows, reusable systems, or measurable delegation to AI.</p><p>I summarized those results back in the Copilot community:</p><p><a href="https://www.reddit.com/r/microsoft_365_copilot/s/Uv9TIiVBiz?utm_source=chatgpt.com">The scores were all over the place, but Copilot’s reasons were surprisingly similar</a></p><p>By then, I wasn’t particularly interested in whether my own Copilot score was high or low.</p><p>For the record, it was <strong>78</strong>.</p><p>What interested me was why it wasn’t 90.</p><h3>What exactly are we calling “advanced AI use”?</h3><p>My own way of using AI is fairly human-driven.</p><p>I spend a lot of time questioning answers, changing assumptions, comparing alternatives, bringing in information the AI doesn’t have, and using the conversation to develop an idea.</p><p>Sometimes the most useful part happens after I stop using AI entirely. I walk away, make a connection later, and bring that connection back into the conversation.</p><p>From my perspective, that can be a fairly deep use of AI.</p><p>But it isn’t necessarily automation.</p><p>And that is where this little experiment became more interesting to me.</p><p>Copilot often seemed to treat the upper end of the scale as a progression from:</p><p><strong>How well do you use AI to do your work?</strong></p><p>toward:</p><p><strong>How much of your work now operates through AI?</strong></p><p>Those are related, but I’m not convinced they are the same thing.</p><p>Someone might use AI very deeply as a reviewer, critic, research partner or thinking partner while deliberately keeping the human in control of the loop.</p><p>Someone else might build highly automated workflows that delegate much more work to AI.</p><p>Which one is the more “advanced AI user”?</p><p>I’m no longer sure that question has a one-dimensional answer.</p><p>Maybe there isn’t one ladder from Level 1 to Level 100.</p><p>There may be several dimensions: depth of interaction, breadth of use, critical evaluation, automation, integration, delegation, creation of reusable systems, and perhaps others.</p><p>A single number collapses all of that into something that looks precise but really isn’t.</p><p>Ironically, asking for that number was what made those hidden assumptions easier to see.</p><h3>I’m not repeating the ChatGPT experiment yet</h3><p>The obvious next step would be to go back to r/ChatGPT, hide my own score, use the more critical prompt, and try again.</p><p>I’m deliberately not doing that yet.</p><p>The original 92/100 post is still recent. Some people may remember it. Repeating the experiment immediately wouldn’t really remove the anchor. It would just hide it one step further away.</p><p>So I’ll leave some distance before trying that again.</p><p>For now, the experiment has already changed the question I want to ask.</p><p>I started with:</p><p><strong>“What level AI user am I?”</strong></p><p>Now I’m more interested in:</p><p><strong>“What does an AI think an advanced AI user looks like?”</strong></p><p>And perhaps an even better question is:</p><p><strong>“What kind of AI user do I actually want to become?”</strong></p><p>Those are very different questions.</p><p>Thanks to everyone in both Reddit communities who tried the prompts, posted their results, challenged the premise, or pointed out problems with the experiment.</p><p>The criticism was probably more useful than the scores.</p><p>I went looking for a number.</p><p>I came back with a better question.</p><h3><strong>More from me</strong></h3><p>I write about thinking with AI, rediscovering old ideas, and experimenting with new ones.</p><p>You can find my other stories here:</p><p><a href="https://medium.com/@noborutakahashi/series-thinking-with-ai-fe99775685a1?sharedUserId=noborutakahashi"><strong>Explore my stories →</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7661d6e4dd0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some of My Best Ideas Happen After I Close ChatGPT]]></title>
            <link>https://medium.com/@noborutakahashi/some-of-my-best-ideas-happen-after-i-close-chatgpt-13fa6aebeb60?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/13fa6aebeb60</guid>
            <category><![CDATA[thinking]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sat, 12 Sep 2026 03:51:16 GMT</pubDate>
            <atom:updated>2026-10-14T13:17:38.450Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-HKNPf0ZGo-OHVxHP2W-g.png" /></figure><p>I’ve been using ChatGPT quite heavily since around February this year.</p><p>Not mainly to get answers. I tend to stay in a conversation for a long time: discussing an idea, pushing back, changing assumptions, trying another direction, sometimes going in circles.</p><p>But recently I noticed something strange.</p><p>Some of the best ideas don’t appear during those conversations.</p><p>They appear after I close ChatGPT.</p><p>I might be walking somewhere, taking a shower, or doing something completely unrelated. Then suddenly two things connect.</p><p>Sometimes I go back to the conversation and add that one connection, and the whole discussion changes direction. It isn’t just one more idea added to the pile. Things we had already discussed suddenly fit together differently.</p><p>This happened often enough that I started wondering what was going on.</p><h3>I thought this was about incubation</h3><p>The obvious word was “incubation.”</p><p>The phenomenon itself is nothing new. People have always had ideas after stepping away from a problem. I can remember the same thing happening long before generative AI existed.</p><p>What felt different was the frequency.</p><p>I’m 60 now, and somehow I feel like I’m generating ideas more frequently than I did when I was younger. Some days this happens several times.</p><p>I wondered whether other people had noticed the same thing, so I posted a question to r/ChatGPT:</p><p>“Has anyone noticed more ‘incubation’ of ideas after talking with ChatGPT?”</p><p>I wasn’t trying to prove a theory. I was mostly looking for people who had experienced something similar.</p><p>The first useful correction came quickly.</p><p>One person basically said: this is normal in any creative process.</p><p>Fair enough.</p><p>So I asked a slightly different question: had it become more frequent since they started using AI?</p><p>They said yes. Their explanation was simple: AI is constantly available.</p><p>That answer stayed with me longer than I expected.</p><p>A human thinking partner is rarely available exactly when an idea appears. They also won’t necessarily want to jump from embedded systems to design to psychology to some random thing I saw earlier that day.</p><p>AI will.</p><p>And the conversation can be left unfinished and picked up again later.</p><p>Maybe the unusual thing isn’t incubation itself. Maybe AI simply lets us start many more thinking cycles.</p><h3>“More stuff to chew on”</h3><p>Another commenter described something much closer to my own experience.</p><p>They said they had always had ideas pop up later, but it happened much more frequently since using AI. Their explanation was that they could now explore an idea much further before putting it down.</p><p>Then they used a phrase I liked:</p><blockquote><em>“It’s more like it gives my brain more stuff to chew on.”</em></blockquote><p>That felt right.</p><p>AI doesn’t necessarily have to produce the idea that matters. The conversation can expose alternatives, contradictions, half-formed possibilities and questions.</p><p>Then I leave.</p><p>My brain apparently doesn’t.</p><p>Another commenter called the time after the conversation “integration time.” They suggested that AI can accelerate learning and exploration, while our brains still need time to process what has just happened.</p><p>Someone else had a less academic name for it:</p><blockquote><em>“It’s meat lag.”</em></blockquote><p>That made me laugh, but there may be something important in it.</p><p>That commenter also made another observation. Before AI, they might spend a lot of time fighting syntax, searching for a structure they knew they had used before, or dealing with relatively mechanical problems.</p><p>Now AI can remove some of that friction.</p><p>So when they deliberately step away, it may be because they have reached a decision that they actually need to think about themselves.</p><p>That was a new angle for me.</p><p>Perhaps AI doesn’t just give the brain more material. It may also get us to the genuinely difficult human part of the problem faster.</p><h3>Then I realized I was asking the wrong question</h3><p>One commenter asked me something that changed the direction of the discussion.</p><p>When one of these ideas appears later, is it usually connected to something the AI had already suggested? Or does it come from somewhere completely unexpected?</p><p>I realized I had seen both.</p><p>In one case, all the pieces are already in the conversation.</p><p>AI has effectively put them on the table, but somehow a particular connection between them hasn’t been made. Later, after I step away, I see the same pieces from another perspective.</p><p>Then I bring that connection back.</p><p>Sometimes the AI immediately starts responding from a completely different direction. The interesting part isn’t that I supplied another fact. The new connection changes how the old facts fit together.</p><p>The second pattern is stranger.</p><p>Sometimes the missing piece comes from somewhere completely unrelated.</p><p>A recent example happened while I was working on an old embedded operating system from the 1980s. Separately, I came across WebAssembly while looking at a completely different project. I wasn’t thinking about the old OS at all.</p><p>Then at some point the connection appeared:</p><p>Could WebAssembly be useful there too?</p><p>Whether that particular idea turns out to be useful isn’t really the point. What interested me was where the connection came from. The AI conversation and the outside experience had become part of the same thinking process, even though they happened at different times and in different contexts.</p><p>At that point, “incubation” started to feel too narrow.</p><h3>So I asked Reddit again</h3><p>I posted a second question, this time without putting incubation at the center:</p><p>“Using AI without relying on it — some of my best ideas come after I close ChatGPT”</p><p>The responses became more varied.</p><p>One person described using ChatGPT for email drafts, then rejecting phrases they would never use and rewriting them into their own voice.</p><p>They wrote:</p><blockquote><em>“I’m a natural editor. Chat gives me something to edit.”</em></blockquote><p>I liked that because it described another version of something I’ve been doing myself.</p><p>I increasingly prefer giving AI something to transform rather than asking it to create something from nothing.</p><p>A rough idea becomes a discussion.<br> Bullet points become prose.<br> An existing implementation becomes a port.<br> One perspective becomes another perspective.</p><p>The useful part often happens when I look at the transformation and think, no, that isn’t quite right.</p><p>That reaction gives me the next constraint.</p><p>Another commenter used a completely different metaphor. They described writing their thoughts into ChatGPT as dumping the contents of a junk drawer onto a surface.</p><p>The AI doesn’t necessarily organize it for them.</p><p>But now everything is visible.</p><p>That makes it easier for them to see what might connect.</p><p>This was getting further and further away from my original question about incubation.</p><p>And I thought that was a good sign.</p><h3>Maybe the important part is the loop</h3><p>I used to think of what I was doing as something like “AI Pair Thinking.”</p><p>I’m less sure about the “pair” part now.</p><p>The loop can include a lot more than me and an AI.</p><p>I talk with ChatGPT. I leave the conversation. Something happens in everyday life. I remember an old project. Someone says something at an event. I read a Reddit comment. A completely unrelated technology catches my attention.</p><p>Then one of those things connects with something already on the table.</p><p>I bring it back to AI, and the discussion changes again.</p><p>Even the article you’re reading came out of that process.</p><p>I started with an observation about ideas appearing after AI conversations. I asked Reddit about incubation. The replies changed my question. I took those replies back into my own thinking and into more AI conversations. Then I asked Reddit again from another angle.</p><p>Now I’m writing something different from the article I originally thought I was going to write.</p><p>I don’t have a name for this yet, and I’m not sure I want one.</p><p>What interests me now is the loop itself: put something into AI, walk away, encounter something outside it, make a connection, bring that connection back, and see what changes.</p><p>Maybe one of the more interesting ways to use AI is to spend some time not using it.</p><h3>The Reddit discussions</h3><p>The two Reddit threads that led to this article:</p><p>“Has anyone noticed more ‘incubation’ of ideas after talking with ChatGPT?”<br> <a href="https://www.reddit.com/r/ChatGPT/s/6tGiuS1eQB">Read the original Reddit discussion</a></p><p>“Using AI without relying on it — some of my best ideas come after I close ChatGPT”<br> <a href="https://www.reddit.com/r/ChatGPT/s/sKsyYIPSFw">Read the second Reddit discussion</a></p><h3>More from me</h3><p>I write about thinking with AI, rediscovering old ideas, and experimenting with new ones.</p><p>You can find my other stories here:</p><p><a href="https://medium.com/@noborutakahashi/series-thinking-with-ai-fe99775685a1?sharedUserId=noborutakahashi"><strong>Explore my stories →</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13fa6aebeb60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CHARM-II on Reddit — Discussions Around My 1980s RTOS Project]]></title>
            <link>https://medium.com/@noborutakahashi/charm-ii-on-reddit-discussions-around-my-1980s-rtos-project-5ce344c57c08?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ce344c57c08</guid>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 01:05:49 GMT</pubDate>
            <atom:updated>2026-11-14T03:09:55.939Z</atom:updated>
            <content:encoded><![CDATA[<p>Alongside my Medium articles, I’ve been sharing the CHARM-II reconstruction project with several Reddit communities.</p><p>These discussions have become part of the project itself. Feedback from r/osdev, r/raspberrypipico, r/retrocomputing, and r/embedded has often led me to reconsider the original design and try new directions.</p><p>This page is a chronological index of those discussions.</p><p>November 3, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/pPLAgtDGbb">From my 1986 RTOS to Karqri: What should I visualize next?</a></li><li>r/retrocomputing <br><a href="https://www.reddit.com/r/retrocomputing/s/6SZogjkjhQ">Six months after rediscovering my 1986 RTOS, I’ve released a new RTOS called Karqri</a></li><li>r/embedded<br><a href="https://www.reddit.com/r/embedded/s/mY3kWkcJHo">I built a new RTOS for POSIX and RP2040 from ideas I explored in 1986 — source now available</a></li><li>r/raspberrypipico<br><a href="https://www.reddit.com/r/raspberrypipico/s/LPPHotqjgP">My RP2040 RTOS is now open source — next I’d like to visualize what’s happening inside it</a></li></ul><p>October 10, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/tQV3nczueE">Follow-up: What I learned about VRTX’s equal-priority scheduling in the 1980s</a></li><li>r/retrocomputing <br><a href="https://www.reddit.com/r/retrocomputing/s/Lvr9gsmZuV">Follow-up: Revisiting a 1986 RTOS led me to someone who used VRTX in 1982</a></li><li>r/embedded<br><a href="https://www.reddit.com/r/embedded/s/ARtykbH0eC">Follow-up: Why my 1986 RTOS survived a simplistic interpretation of VRTX scheduling</a></li></ul><p>September 9, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/h6PG9bZO7a">Why did VRTX change equal-priority scheduling from newest-first to FIFO?</a></li><li>r/retrocomputing <br><a href="https://www.reddit.com/r/retrocomputing/s/vnT1JWZRtQ">I found out that VRTX changed its scheduling behavior just after I used it as a reference in 1986 — does anyone know why?</a></li><li>r/embedded<br><a href="https://www.reddit.com/r/embedded/s/gMr2klUiCY">Did anyone here use VRTX in the 1980s? Why did equal-priority scheduling change to FIFO?</a></li></ul><p>August 17, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/qmDlyXUTow">My 1986 RTOS is now preemptively multitasking on a Raspberry Pi Pico — and it made me question whether I need an RTOS</a></li><li>r/retrocomputing<br><a href="https://www.reddit.com/r/retrocomputing/s/mwaEaVQrJw">My 1986 RTOS is now fully preemptive on a Raspberry Pi Pico — and it changed how I think about the original design</a></li><li>r/raspberrypipico<br><a href="https://www.reddit.com/r/raspberrypipico/s/JYkPTcE9VN">My 1986 RTOS is now running six preemptive tasks on a Raspberry Pi Pico</a></li></ul><p>August 1, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/gthHF6vBrl">The First Original CHARM-II Kernel Code Running on Raspberry Pi Pico</a></li><li><a href="https://www.reddit.com/r/retrocomputing/s/8xwSuuUwFX">r/retrocomputing<br>The First Original CHARM-II Kernel Code Running on Raspberry Pi Pico</a></li><li>r/raspberrypipico<br><a href="https://www.reddit.com/r/raspberrypipico/s/DELB3i0hnv">Porting My 1986 RTOS to Raspberry Pi Pico — First Kernel Functions Running</a></li></ul><p>July 5, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/ALUFHn9jDi">Rediscovering the Development Methodology Behind My 1986 RTOS</a></li><li>r/retrocomputing<br><a href="https://www.reddit.com/r/retrocomputing/s/oa1Sfws9kR">Rediscovering the Development Workflow Behind My 1986 RTOS</a></li></ul><p>June 13, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/s/bBYEowTSvM">Visualizing a 1986 RTOS in a Modern Browser</a></li><li>r/retrocomputing<br><a href="https://www.reddit.com/r/retrocomputing/s/S4fS72tvaQ">Rediscovering My 1986 RTOS Development Environment 40 Years Later</a></li></ul><p>June 6, 2026</p><ul><li>r/osdev<br><a href="https://www.reddit.com/r/osdev/comments/1ty739z/rediscovered_a_40yearold_68000_rtos_source_tree/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">Rediscovered a 40-year-old 68000 RTOS source tree — now rebuilding it on POSIX with AI assistance</a></li><li>r/retrocomputing<br><a href="https://www.reddit.com/r/retrocomputing/comments/1ty7d7b/40_years_later_recreating_my_sun2_68000_workflow/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">40 years later: recreating my SUN-2 ↔ 68000 workflow with WSL2 and Raspberry Pi Pico</a></li></ul><p>June 2, 2026</p><ul><li>r/retrocomputing<br><a href="https://www.reddit.com/r/retrocomputing/comments/1tso9zs/i_finally_figured_out_why_most_of_my_1980s_rtos/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">I finally figured out why most of my 1980s RTOS never got rewritten in assembly</a></li><li>r/embedded<br><a href="https://www.reddit.com/r/embedded/comments/1tsohgw/a_performance_problem_that_never_happened_kept/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">A performance problem that never happened kept this RTOS alive for 40 years</a><br>(deleted)</li></ul><p>May 26, 2026</p><ul><li>r/embedded<br><a href="https://www.reddit.com/r/embedded/comments/1to9329/recreated_a_cooperative_rtos_track_demo_from_40/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">Recreated a cooperative RTOS track demo from 40 years ago on POSIX</a></li><li>r/retrocomputing<br><a href="https://www.reddit.com/r/retrocomputing/comments/1to8zor/40_years_later_old_whitesmithsstyle_c/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">40 years later, old Whitesmiths-style C unexpectedly made my RTOS portable to POSIX</a></li></ul><p>May 25, 2026</p><ul><li>r/embedded<br><a href="https://www.reddit.com/r/embedded/comments/1tmhvoq/rebuilding_a_1980s_68000_embedded_rtos_workflow/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button">Rebuilding a 1980s 68000 embedded RTOS workflow on POSIX and Raspberry Pi Pico</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ce344c57c08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Series: 1980s Real Time OS]]></title>
            <link>https://medium.com/@noborutakahashi/series-1980s-real-time-os-fd24fc389274?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd24fc389274</guid>
            <category><![CDATA[real-time-os]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 08:32:24 GMT</pubDate>
            <atom:updated>2026-11-14T03:25:08.746Z</atom:updated>
            <content:encoded><![CDATA[<h3>Series: Revisiting a 40-Year-Old System</h3><ul><li><a href="https://medium.com/@noborutakahashi/a-40-year-old-system-analyzed-with-ai-it-turned-out-to-have-a-modern-architecture-83751821bf5a">When I analyzed a 40-year-old system with AI, it looked just like modern architecture</a></li><li><a href="https://medium.com/@noborutakahashi/a-40-year-old-memory-map-comparable-to-todays-raspberry-pi-pico-932c4309260d">How a 1980s Memory Map Compares to a Modern Raspberry Pi Pico</a></li><li><a href="https://medium.com/@noborutakahashi/an-era-when-almost-everything-was-my-code-charm-ii-and-bare-metal-systems-0394fb119744">An Era When Almost Everything Was My Code — CHARM-II and Bare-Metal Systems</a></li><li><a href="https://medium.com/@noborutakahashi/why-90-of-my-1980s-rtos-survived-in-c-for-40-years-3ff6d524eb4a?sharedUserId=noborutakahashi">Why 90% of My 1980s RTOS Survived in C for 40 Years</a></li></ul><h3>Series: Bringing a 40-Year-Old System to Life Today</h3><ul><li><a href="https://medium.com/@noborutakahashi/reconstructing-a-1986-rtos-rediscovering-a-40-year-old-development-methodology-d336a2657939?sharedUserId=noborutakahashi">Reconstructing a 1986 RTOS: Rediscovering a 40-Year-Old Development Methodology</a></li><li><a href="https://medium.com/@noborutakahashi/i-ported-a-40-year-old-rtos-to-a-raspberry-pi-pico-then-started-questioning-the-rtos-itself-35a141d96901?sharedUserId=noborutakahashi">I Ported a 40-Year-Old RTOS to a Raspberry Pi Pico — Then Started Questioning the RTOS Itself</a></li><li><a href="https://medium.com/@noborutakahashi/i-revisited-my-40-year-old-rtos-and-met-someone-who-used-vrtx-in-1982-615473044a50?sharedUserId=noborutakahashi">I Revisited My 40-Year-Old RTOS — and Met Someone Who Used VRTX in 1982</a></li><li><a href="https://medium.com/@noborutakahashi/revisiting-a-40-year-old-rtos-how-github-and-reddit-helped-shape-its-next-direction-7eb06ebbd9d4?sharedUserId=noborutakahashi">Revisiting a 40-Year-Old RTOS: How GitHub and Reddit Helped Shape Its Next Direction</a></li></ul><h3>Discussions on Reddit</h3><p>I’ve also been sharing the CHARM-II project on Reddit, where discussions with the r/osdev, r/raspberrypipico, r/retrocomputing, and r/embedded communities have influenced how the project has evolved.</p><p>I’ve collected those posts and discussions here:</p><p><a href="https://medium.com/@noborutakahashi/charm-ii-on-reddit-discussions-around-my-1980s-rtos-project-5ce344c57c08?postPublishedType=repub"><strong>CHARM-II on Reddit — Discussions Around My 1980s RTOS Project</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd24fc389274" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Ported a 40-Year-Old RTOS to a Raspberry Pi Pico — Then Started Questioning the RTOS Itself]]></title>
            <link>https://medium.com/@noborutakahashi/i-ported-a-40-year-old-rtos-to-a-raspberry-pi-pico-then-started-questioning-the-rtos-itself-35a141d96901?source=rss-13cd3e66f83e------2</link>
            <guid isPermaLink="false">https://medium.com/p/35a141d96901</guid>
            <category><![CDATA[embedded-systems]]></category>
            <category><![CDATA[operating-systems]]></category>
            <category><![CDATA[c-programming]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[raspberry-pi-pico]]></category>
            <dc:creator><![CDATA[Noboru Takahashi]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 02:20:48 GMT</pubDate>
            <atom:updated>2026-10-10T07:05:59.307Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MVDhpC5Cv_OKaHGssNWWmw.png" /></figure><p>About 40 years ago, I built an RTOS as part of my job.</p><p>It was called <strong>CHARM-II</strong>, developed in 1986 for a Motorola 68000 target. Our development environment was based on a Sun-2 workstation.</p><p>Recently, I rediscovered the original source code and documentation and started studying the system again, with the help of modern AI tools.</p><p>At first, the goal seemed simple:</p><p><strong>Can I bring this 40-year-old RTOS back to life on modern hardware?</strong></p><p>Eventually, I got a minimal version running on a Raspberry Pi Pico.</p><p>And that led to a question I hadn’t expected.</p><p><strong>Do I still need to build it this way?</strong></p><h3>Getting preemptive context switching running on the Pico</h3><p>The current Pico version is still minimal, but it now runs multiple independent tasks, invokes the scheduler from a timer interrupt, and performs preemptive context switching.</p><p><a href="https://www.youtube.com/watch?v=AYm1PGx-diU">YouTube video</a><br>(Video 1: A 40-Year-Old RTOS Running Preemptively on Raspberry Pi Pico)</p><p>For visualization, I created a small “track” demo. Tasks A through F move independently around tracks and pass through a shared critical zone.</p><p>It is partly a demonstration and partly a debugging tool: I can actually watch scheduling and synchronization behavior.</p><p>Seeing concepts from an RTOS I worked on in 1986 running again on a tiny modern microcontroller was satisfying.</p><p>But once it worked, I found myself wondering:</p><p><strong>Is preemptive context switching still necessary here?</strong></p><h3>The Pico is fast. Maybe a superloop is enough?</h3><p>Compared with the hardware we had 40 years ago, even a small Raspberry Pi Pico is extraordinarily capable.</p><p>Of course, “the CPU is faster now” does not automatically mean that an RTOS is unnecessary.</p><p>But while watching the system run, I started thinking about how much could simply be handled by a fast superloop.</p><p>If the main loop can cycle through everything in around a millisecond, many embedded applications may be perfectly happy with that.</p><p>So why maintain separate task stacks, save and restore contexts from interrupts, and introduce preemption at all?</p><p>This was something I had barely questioned when working on RTOSes decades ago.</p><p>Actually running the old design on modern hardware made the question much harder to ignore.</p><p>So I posted the question to Reddit, particularly in r/raspberrypipico and r/osdev.</p><p>The answers changed the way I was thinking about the problem.</p><h3>It isn’t “superloop vs. RTOS”</h3><p>One of my assumptions was that the design space looked something like this:</p><p><strong>superloop → preemptive RTOS</strong></p><p>But several people pointed out that there is a lot of territory in between.</p><p>There is cooperative multitasking, where tasks explicitly yield rather than being involuntarily preempted.</p><p>There are event-driven and run-to-completion designs, where work is triggered by events and handlers execute without requiring a separate stack and execution context for every logical task.</p><p>There are also hybrid approaches.</p><p>The question of <strong>which task should run next</strong> is not necessarily the same question as <strong>how control should be transferred when another task becomes ready</strong>.</p><p>Those decisions can be separated.</p><p>That sounds obvious when written down.</p><p>But it made me realize that I had been carrying around a rather rigid mental model of an “RTOS” for a very long time.</p><h3>CPU speed wasn’t really the important question</h3><p>Another important point from the discussion was that CPU performance alone is the wrong metric.</p><p>The real questions include:</p><ul><li>How deterministic does the system need to be?</li><li>How much jitter is acceptable?</li><li>What are the latency requirements?</li><li>How complex is the application?</li><li>How much shared state exists?</li><li>What does preemption actually buy us for this particular system?</li></ul><p>A system may work perfectly well with a 1 ms loop.</p><p>Another system may fail because 100 µs of timing jitter is unacceptable.</p><p>Average execution speed and timing guarantees are not the same thing.</p><p>Again, none of this is new RTOS theory.</p><p>What was new was being forced to reconsider it while looking at a system whose basic architecture I had first designed 40 years ago.</p><h3>Maybe my idea of an RTOS stopped evolving 40 years ago</h3><p>I summarized some of the Reddit discussion in a Japanese OS development community, osdev-jp.</p><p>Someone there raised another question that stayed with me:</p><p>Why do we so easily equate an <strong>embedded OS</strong> with an <strong>RTOS</strong>?</p><p>For many applications, cooperative multitasking or a lightweight execution model may be entirely adequate.</p><p>That made me realize something slightly uncomfortable.</p><p>My mental image of an RTOS may not have evolved very much since I was building one in the 1980s.</p><p>Timer interrupt.</p><p>Save the current task context.</p><p>Run the scheduler.</p><p>Restore another task’s context.</p><p>Resume execution.</p><p>That architecture is still perfectly valid.</p><p>But if I were designing an embedded operating system from scratch in 2026, is that necessarily where I would start?</p><p>That is a much more interesting question.</p><h3>From restoring CHARM-II to designing CHARM-II 2026</h3><p>Originally, I wanted to reconstruct CHARM-II as faithfully as possible.</p><p>I still want to preserve and understand the original system. There is value in seeing exactly how it worked and why it was designed that way.</p><p>But simply reproducing the 1986 architecture no longer feels sufficient.</p><p>Instead, I want to ask:</p><p><strong>What would CHARM-II look like if I designed it in 2026?</strong></p><p>That does not necessarily mean turning it into a conventional modern preemptive RTOS.</p><p>I want to experiment.</p><p>What happens if the same small application is implemented using:</p><ul><li>a superloop,</li><li>an event-driven/run-to-completion model,</li><li>cooperative multitasking,</li><li>preemptive multitasking,</li><li>or some hybrid of these?</li></ul><p>How does the code change?</p><p>How does latency change?</p><p>How much complexity moves into the kernel, and how much moves into the application?</p><p>At what point does preemption become useful enough to justify its cost?</p><p>These questions seem more interesting to me now than simply proving that a 40-year-old scheduler can still run.</p><h3>The next step: publish the smallest working version</h3><p>Before experimenting further, I want to clean up the minimal Pico version that is running now and publish it on GitHub.</p><p>Not as a finished “CHARM-II 2026.”</p><p>Quite the opposite.</p><p>I want it to be the <strong>starting point</strong>.</p><p>Once the code is public, discussions can become much more concrete.</p><p>Instead of debating abstractly whether preemption is necessary, we can look at actual code and ask:</p><p>Could this part be cooperative?</p><p>Would an event-driven implementation be simpler?</p><p>What happens if we remove the context switch?</p><p>What should remain from the original CHARM-II design, and what should be reconsidered after 40 years?</p><p>I started this project because I wanted to bring an old RTOS back to life.</p><p>Somewhere along the way, the question changed.</p><p>Now I find myself asking:</p><p><strong>If I were building it today, what should an embedded OS actually be?</strong></p><p>That seems like a much more interesting experiment.</p><p>To be continued.</p><h3><a href="https://medium.com/@noborutakahashi/series-1980s-real-time-os-fd24fc389274?sharedUserId=noborutakahashi"><strong>Related Reading<br>1980s Real-Time-OS — Article Series</strong></a></h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35a141d96901" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>