<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>FarmakoMed Engineering Journal</title>
    <link>https://farmakomed.eu/engineering-journal/</link>
    <description>Building privacy-first, on-device AI for healthcare. Real engineering, real lessons.</description>
    <language>en</language>
    <lastBuildDate>Tue, 21 Jul 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://farmakomed.eu/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Diagnostics Without Telemetry</title>
      <link>https://farmakomed.eu/engineering-journal/diagnostics-without-telemetry.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/diagnostics-without-telemetry.html</guid>
      <description>Debugging on-device AI when you can&apos;t rely on server logs or remote sessions. Why a privacy-first architecture has to redesign diagnostics around the device instead of abandoning them, and what that redesign actually requires.</description>
      <pubDate>Tue, 21 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-21T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>We Tried a Bigger Model. Here&apos;s Why We Shelved It.</title>
      <link>https://farmakomed.eu/engineering-journal/we-tried-a-bigger-model-heres-why-we-shelved-it.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/we-tried-a-bigger-model-heres-why-we-shelved-it.html</guid>
      <description>A health-specialized language model looked like an obvious upgrade. Getting an honest answer about whether it belonged in the app meant fixing a missing off-ramp, un-rigging our own test, and finally watching a GPU delegate fail to compile the model, twice, identically.</description>
      <pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-16T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>The Problem Was Never the GPU</title>
      <link>https://farmakomed.eu/engineering-journal/the-problem-was-never-the-gpu.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/the-problem-was-never-the-gpu.html</guid>
      <description>A real performance investigation into slow on-device AI inference started with the obvious suspect: the GPU. It ended somewhere nobody expected, a lifecycle policy rebuilding the inference engine on almost every scan — and, on a second pass with a production device and real numbers, a deliberate memory trade-off nobody had re-measured, plus a hard look at whether the phone&apos;s GPU and NPU could do any better. A story about optimizing the wrong layer, twice.</description>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-14T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>LLMs vs SLMs: Why Bigger Isn&apos;t Always Better</title>
      <link>https://farmakomed.eu/engineering-journal/llms-vs-slms-why-bigger-isnt-always-better.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/llms-vs-slms-why-bigger-isnt-always-better.html</guid>
      <description>The AI industry is obsessed with parameter counts. But model size is only one dimension of quality. The real engineering challenge isn&apos;t finding the biggest model. It&apos;s choosing the right one for the task. An argument for architectural balance between Large and Small Language Models.</description>
      <pubDate>Thu, 09 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-09T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Democratizing AI: Billions of Phones, One Distributed Intelligence</title>
      <link>https://farmakomed.eu/engineering-journal/democratizing-ai.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/democratizing-ai.html</guid>
      <description>How Small Language Models and Edge AI could make artificial intelligence accessible to billions of people, not only to those with powerful hardware or continuous cloud subscriptions. FarmakoMed as a practical case study.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-08T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Every System Needs a Deliberate Exit Door</title>
      <link>https://farmakomed.eu/engineering-journal/every-system-needs-a-deliberate-exit-door.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/every-system-needs-a-deliberate-exit-door.html</guid>
      <description>Developers spend enormous effort protecting how data enters a system, and almost none designing how it leaves. Exports, backups, reports and logs are the weakest part of most secure architectures. A practical guide to designing outbound trust boundaries.</description>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-08T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Battery-Aware AI Inference on Mobile: Why Energy Is an Architectural Decision</title>
      <link>https://farmakomed.eu/engineering-journal/battery-aware-ai-inference-on-mobile.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/battery-aware-ai-inference-on-mobile.html</guid>
      <description>Local AI moves computation from the data centre into the user&apos;s pocket, and the battery becomes part of the architecture. An engineering look at why energy is a first-class design constraint for on-device AI, with FarmakoMed as the case study.</description>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-07T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Building Self-Healing Android Applications: Why Keeping an App Alive Should Never Make It Slower</title>
      <link>https://farmakomed.eu/engineering-journal/building-self-healing-android-applications.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/building-self-healing-android-applications.html</guid>
      <description>A warm Android process shouldn&apos;t get slower just for staying alive. An engineering look at runtime recovery, treating a long background stay as a health check instead of waiting for a restart, with FarmakoMed as the real-world case study.</description>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-07T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Can AI Be Sustainable?: Measuring Intelligence by More Than Benchmarks</title>
      <link>https://farmakomed.eu/engineering-journal/can-ai-be-sustainable.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/can-ai-be-sustainable.html</guid>
      <description>AI is measured by benchmark scores, reasoning quality, and context windows, rarely by the energy an answer required. An engineering look at whether sustainability deserves a seat alongside performance, accuracy, latency, cost, and privacy, with FarmakoMed as one example of a different architecture.</description>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-07T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>The Engine Isn&apos;t the Car: Why Architectural Independence Matters More Than Technology Choices</title>
      <link>https://farmakomed.eu/engineering-journal/the-engine-isnt-the-car.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/the-engine-isnt-the-car.html</guid>
      <description>FarmakoMed runs Google&apos;s Gemma on-device. Does that make it &apos;a Google product&apos;? An engineering essay on why architecture, not the choice of any single component, is what technological sovereignty actually means.</description>
      <pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-05T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>AI Should Wait for the User, Not the Other Way Around</title>
      <link>https://farmakomed.eu/engineering-journal/ai-should-wait-for-the-user.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/ai-should-wait-for-the-user.html</guid>
      <description>Why building seamless on-device AI forced us to redesign our application architecture instead of our machine learning models, a retrospective on lifecycle coupling.</description>
      <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-04T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>The Hidden Cost of AI Isn&apos;t Compute. It&apos;s Dependency.</title>
      <link>https://farmakomed.eu/engineering-journal/the-hidden-cost-of-ai-isnt-compute-its-dependency.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/the-hidden-cost-of-ai-isnt-compute-its-dependency.html</guid>
      <description>AI quietly introduced a new economic unit, the token. An essay on what it means to rent intelligence by the request, and whether that should be the only model.</description>
      <pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-03T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Choosing a Model for On-Device Healthcare AI</title>
      <link>https://farmakomed.eu/engineering-journal/choosing-a-model-for-on-device-healthcare-ai.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/choosing-a-model-for-on-device-healthcare-ai.html</guid>
      <description>Why selecting the &apos;best&apos; language model is less important than understanding your product constraints, a practical look at on-device model selection using FarmakoMed as the case study.</description>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-02T00:00:00Z</atom:updated>
    </item>
    <item>
      <title>Privacy by Architecture</title>
      <link>https://farmakomed.eu/engineering-journal/privacy-by-architecture.html</link>
      <guid isPermaLink="true">https://farmakomed.eu/engineering-journal/privacy-by-architecture.html</guid>
      <description>Why local AI changes software architecture, not just privacy policies. When medical data never leaves the device, an entire category of risk disappears with it.</description>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <atom:updated>2026-07-01T00:00:00Z</atom:updated>
    </item>
  </channel>
</rss>
