<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Llm on Akshay Deshpande</title>
    <link>https://akshayd-dev.pages.dev/tags/llm/</link>
    <description>Recent content in Llm on Akshay Deshpande</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Oct 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://akshayd-dev.pages.dev/tags/llm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Encoding: From the POV of Dataflow paths</title>
      <link>https://akshayd-dev.pages.dev/posts/encoding-from-the-pov-of-dataflow-paths/</link>
      <pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://akshayd-dev.pages.dev/posts/encoding-from-the-pov-of-dataflow-paths/</guid>
      <description>&lt;p&gt;When studying Chapter 4 of &lt;em&gt;&lt;strong&gt;Designing Data-Intensive Applications&lt;/strong&gt;&lt;/em&gt; (Encoding and Evolution), I quickly encounters a level of granularity that seems &lt;em&gt;mechanical&lt;/em&gt;: binary formats, schema evolution, and serialization techniques. Yet behind this technical scaffolding lies something conceptually deeper. Encoding is not merely a process of serialization; it is the very grammar through which distributed systems express and interpret meaning. It is the act that allows a system’s internal thoughts — the data in memory — to be externalized into a communicable form. Without it, a database, an API, or a Kafka stream would be nothing but incomprehensible noise.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
