<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Qwen on Fabian G. Williams</title>
    <link>https://www.fabswill.com/tags/qwen/</link>
    <description>Recent content in Qwen on Fabian G. Williams</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.fabswill.com/tags/qwen/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Doug Was Right: I Swapped In The MoE, And The Concurrency Math Changed</title>
      <link>https://www.fabswill.com/blog/doug-was-right-i-measured-the-moe/</link>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/doug-was-right-i-measured-the-moe/</guid>
      <description>Two days ago I posted 36 barrier-synchronized loads against 1 local model and let the numbers answer a question Reddit handed me. That post ended with a promise. A reader named Doug Ware, who builds applied AI systems for a living, had replied with the one caveat I had not tested, and I said out loud that measuring it was the next thing I would do. This is that measurement.</description>
    </item>
    
    <item>
      <title>You Asked, So I Measured: What Concurrency Actually Costs On One Local Model</title>
      <link>https://www.fabswill.com/blog/you-asked-i-measured-the-concurrency-ceiling/</link>
      <pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/you-asked-i-measured-the-concurrency-ceiling/</guid>
      <description>Over last week and these last 2 days in this week I posted measured answers to readers both in Twitter and Reddit who asked whether my experiments of 2 local agents on 1 Mac run in parallel or take turns. The answers was that they share one continuous batch, batching is real, and 3 quiet choices collapse it. I thought that was the end of it. It was not. The comments were better than my post, WHICH IS AWESOME, becaue this is the crowdsourcing of brain power I love.</description>
    </item>
    
    <item>
      <title>I Added a Second Local Agent This Week. Here Is the Receipt for Every Human Decision Behind It.</title>
      <link>https://www.fabswill.com/blog/i-added-a-second-local-agent-and-kept-the-receipt/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/i-added-a-second-local-agent-and-kept-the-receipt/</guid>
      <description>This week I trialed a second local coding agent, Hermes from Nous Research, on my own MacBook Pro M3 Max, pointed at the same local Qwen 3.8 model I already run. I installed it additively, so nothing already working could break, governed it with manual approvals, and did not stop until it proved it behaves. Here is the trial, in tables and screenshots.
One housekeeping note before the story. Last week&amp;rsquo;s post got called AI slop on Reddit.</description>
    </item>
    
    <item>
      <title>Two Agents, One Local Model: Do They Run in Parallel, or Take Turns? I Measured It.</title>
      <link>https://www.fabswill.com/blog/two-agents-one-local-model-batching/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/two-agents-one-local-model-batching/</guid>
      <description>A reader on Reddit asked me a sharp question about my last post. I had trialed a second local coding agent, Hermes, pointed at the same local Qwen 3.8 model my other agent already uses. His question was simple. Did I ever run both agents at the same time, two separate harnesses hammering one model on one Mac at once. And what about Hermes spawning its own sub-agents against that same endpoint.</description>
    </item>
    
    <item>
      <title>I Swapped My Local Coding Model Overnight From a Hotel. The Agent Graded the Upgrade Itself.</title>
      <link>https://www.fabswill.com/blog/local-model-upgrade-qwen-38-agent-self-tested/</link>
      <pubDate>Sat, 15 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/local-model-upgrade-qwen-38-agent-self-tested/</guid>
      <description>TL;DR Local models are how I run my community work, my volunteer projects, my side hustles, and my musings. Two reasons, both simple:
 Cost. None of this work should bill against a frontier account. Trust. Client and customer data stays on my own disk, away from the labs.  Bottom line up front: I am running Qwen3.8-27B (4-bit) on my MacBook Pro M3 Max, 128 GB of unified memory and a 40-core GPU, my personal dev rig, driven by an OpenCode harness.</description>
    </item>
    
    <item>
      <title>Replacing gpt-oss:120b With Qwen3.6 on a MacBook Pro: A Two-Day Local Model Benchmark</title>
      <link>https://www.fabswill.com/blog/replacing-gpt-oss-with-qwen3-6-on-macbook-pro/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://www.fabswill.com/blog/replacing-gpt-oss-with-qwen3-6-on-macbook-pro/</guid>
      <description>TL;DR I spent two days benchmarking three Qwen3.6 variants against gpt-oss:120b on my MacBook Pro M3 Max. The shocking result: a 21 GB coding-tuned model ran an OpenClaw-shaped research-brief workload that I use for the non profit MACONA.org in 6 seconds — 10x faster than gpt-oss:120b on the same prompt. Fast enough that I now have reasonable confidence I could move this kind of work off the SaaS-hosted frontier models I have been paying for and onto local hardware on my dev machine.</description>
    </item>
    
  </channel>
</rss>