<?xml version="1.0" encoding="UTF-8"?>
<!-- generated by src/pages/feeds/[domain].xml.ts -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Science DNA</title>
    <link>https://dsdna.pinnacletechsolutions.co.uk/blog/</link>
    <description>Latest articles from Data Science DNA.</description>
    <language>en-GB</language>
    <atom:link href="https://assets.pinnacletechsolutions.co.uk/feeds/ds.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Feature Stores Without the Hype</title>
      <link>https://dsdna.pinnacletechsolutions.co.uk/blog/feature-stores-without-the-hype/</link>
      <guid isPermaLink="true">https://dsdna.pinnacletechsolutions.co.uk/blog/feature-stores-without-the-hype/</guid>
      <description>A feature store keeps training and serving features consistent. Here is when a team genuinely needs one, and when a plain Postgres table already does the job.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
      <author>Vedad Sabljic</author>
      <category>mlops</category>
      <category>data-engineering</category>
    </item>
    <item>
      <title>Reading Model Output As A Business Case</title>
      <link>https://badna.pinnacletechsolutions.co.uk/blog/reading-model-output-as-a-business-case/</link>
      <guid isPermaLink="true">https://badna.pinnacletechsolutions.co.uk/blog/reading-model-output-as-a-business-case/</guid>
      <description>A model output is not a decision. Covers expected value, error-type cost asymmetry, and why a threshold is a commercial choice, not a modelling one.</description>
      <pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate>
      <author>Vedad Sabljic</author>
      <category>business-cases</category>
      <category>experimentation</category>
      <category>governance</category>
    </item>
  </channel>
</rss>
