<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>Notes: David Mashiah</title>
  <link href="https://davidmashiah.com/feed.xml" rel="self"/>
  <link href="https://davidmashiah.com/"/>
  <id>https://davidmashiah.com/feed.xml</id>
  <updated>2026-07-28T00:00:00Z</updated>
  <author><name>David Mashiah</name><uri>https://davidmashiah.com</uri></author>
  <entry>
    <title>The training set moves the error 390x. Nothing predicts it.</title>
    <link href="https://davidmashiah.com/notes/training-set-choice-moves-the-error"/>
    <id>https://davidmashiah.com/notes/training-set-choice-moves-the-error</id>
    <updated>2026-07-28T00:00:00Z</updated>
    <published>2026-07-28T00:00:00Z</published>
    <summary>Across 231 training-set choices the worst case moved by a factor of 390. I tested nine cheap ways to pick a good one. None of them held up.</summary>
    <category term="machine-learning"/>
    <category term="measurement"/>
  </entry>
  <entry>
    <title>The metric was measuring my model, not the problem</title>
    <link href="https://davidmashiah.com/notes/the-metric-was-measuring-my-model"/>
    <id>https://davidmashiah.com/notes/the-metric-was-measuring-my-model</id>
    <updated>2026-07-28T00:00:00Z</updated>
    <published>2026-07-28T00:00:00Z</published>
    <summary>A transferability score held at 0.54 across two independent budgets, then collapsed to 0.14 when I changed the model class. It was tracking the algorithm.</summary>
    <category term="machine-learning"/>
    <category term="measurement"/>
  </entry>
  <entry>
    <title>You cannot count the sale you did not make</title>
    <link href="https://davidmashiah.com/notes/the-sale-you-did-not-make"/>
    <id>https://davidmashiah.com/notes/the-sale-you-did-not-make</id>
    <updated>2026-07-27T00:00:00Z</updated>
    <published>2026-07-27T00:00:00Z</published>
    <summary>Sales data records what you sold, not what people wanted. The two differ exactly on the days they matter most, and the gap teaches a forecast to shrink.</summary>
    <category term="supply-chain"/>
    <category term="measurement"/>
    <category term="machine-learning"/>
  </entry>
  <entry>
    <title>A scratched label still scans, and that is not luck</title>
    <link href="https://davidmashiah.com/notes/a-scratched-label-still-scans"/>
    <id>https://davidmashiah.com/notes/a-scratched-label-still-scans</id>
    <updated>2026-07-27T00:00:00Z</updated>
    <published>2026-07-27T00:00:00Z</published>
    <summary>A check digit tells you a barcode scan was wrong. Reed–Solomon parity tells you what it should have been. That difference decides what a damaged label costs.</summary>
    <category term="coding-theory"/>
    <category term="supply-chain"/>
    <category term="measurement"/>
  </entry>
  <entry>
    <title>Why a screen cannot measure vernier acuity, and how close it gets</title>
    <link href="https://davidmashiah.com/notes/why-a-screen-cannot-measure-vernier-acuity"/>
    <id>https://davidmashiah.com/notes/why-a-screen-cannot-measure-vernier-acuity</id>
    <updated>2026-07-25T00:00:00Z</updated>
    <published>2026-07-23T00:00:00Z</published>
    <summary>A screen pixel at 60 cm subtends about 90 arcseconds; clinical vernier thresholds are 2–5. Antialiasing still measures below one pixel. Here is the arithmetic.</summary>
    <category term="vision-science"/>
    <category term="measurement"/>
  </entry>
  <entry>
    <title>My model scored perfect and that was the problem</title>
    <link href="https://davidmashiah.com/notes/my-model-scored-perfect"/>
    <id>https://davidmashiah.com/notes/my-model-scored-perfect</id>
    <updated>2026-07-25T00:00:00Z</updated>
    <published>2026-07-23T00:00:00Z</published>
    <summary>A perfect held-out score measured one thing: whether the model could repeat what it had seen. Of 30 cross-family tests, 20 fell below a crude baseline.</summary>
    <category term="machine-learning"/>
    <category term="supply-chain"/>
    <category term="measurement"/>
  </entry>
</feed>
