<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: yoey</title>
    <description>The latest articles on DEV Community by yoey (@yoosseph).</description>
    <link>https://dev.to/yoosseph</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4130502%2F302382a4-c76f-49a9-88fa-35867d96467f.jpg</url>
      <title>DEV Community: yoey</title>
      <link>https://dev.to/yoosseph</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yoosseph"/>
    <language>en</language>
    <item>
      <title>Zet: an open-source layer on Laya that knows when to ask a human</title>
      <dc:creator>yoey</dc:creator>
      <pubDate>Wed, 30 Sep 2026 03:10:19 +0000</pubDate>
      <link>https://dev.to/yoosseph/zet-an-open-source-layer-on-laya-that-knows-when-to-ask-a-human-1o6i</link>
      <guid>https://dev.to/yoosseph/zet-an-open-source-layer-on-laya-that-knows-when-to-ask-a-human-1o6i</guid>
      <description>&lt;p&gt;Confidence scores aren't error rates. Zet sits on top of Laya and marks every answer sure or unsure, using conformal prediction sets and a Learn-then-Test threshold calibrated per language, so the answers it automates stay within an error budget you choose (say 5%). On MASSIVE (human-labeled, 300 examples per language, 5% budget), it automated 84% of English and 80% of Swedish requests on a 6-scenario task, with 0 errors in 75 sure English answers. When the task got harder (18 scenarios), it automated nothing, while its prediction sets still contained the right answer 97-99% of the time. That refusal is the feature working. Runs locally on ONNX Runtime with no PyTorch, with a web interface for creating tasks, uploading labeled examples, calibrating, and reviewing unsure answers. Apache-2.0, built on Laya (not endorsed by its authors).&lt;/p&gt;

&lt;p&gt;Site: &lt;a href="https://yoosseph.github.io/Zet/" rel="noopener noreferrer"&gt;https://yoosseph.github.io/Zet/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/Yoosseph/Zet" rel="noopener noreferrer"&gt;https://github.com/Yoosseph/Zet&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>python</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I built an interactive 3D PC anatomy tool to learn what’s actually inside a computer</title>
      <dc:creator>yoey</dc:creator>
      <pubDate>Thu, 17 Sep 2026 21:22:28 +0000</pubDate>
      <link>https://dev.to/yoosseph/i-built-an-interactive-3d-pc-anatomy-tool-to-learn-whats-actually-inside-a-computer-n4m</link>
      <guid>https://dev.to/yoosseph/i-built-an-interactive-3d-pc-anatomy-tool-to-learn-whats-actually-inside-a-computer-n4m</guid>
      <description>&lt;p&gt;I built an interactive 3D PC anatomy tool to learn what’s actually inside a computer&lt;/p&gt;

&lt;p&gt;I’ve been working on an open-source project called PC Anatomy.&lt;/p&gt;

&lt;p&gt;The idea is simple: instead of reading a wall of text about PC components, you can explore a PC visually in 3D, click on the different parts, and learn what each component does.&lt;/p&gt;

&lt;p&gt;I wanted it to feel more like taking apart a computer than reading a hardware guide.&lt;/p&gt;

&lt;p&gt;It’s still something I’m actively improving, so feedback, feature ideas, issues and contributions are very welcome.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Yoosseph/pc-anatomy" rel="noopener noreferrer"&gt;https://github.com/Yoosseph/pc-anatomy&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you find it useful or just like the idea, a star on GitHub would be appreciated - it helps more people find the project.&lt;/p&gt;

&lt;p&gt;I’d also genuinely love to see someone fork it, build on top of it, add new hardware, improve the visuals, or take the idea in a direction I haven’t thought of.&lt;/p&gt;

&lt;p&gt;If you try it, let me know what you think is missing.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>opensource</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
