<?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>Posts on Michal’s Log</title><link>https://michalkordyzon.github.io/posts/</link><description>Recent content in Posts on Michal’s Log</description><generator>Hugo -- 0.164.0</generator><language>en-us</language><lastBuildDate>Sun, 02 Aug 2026 16:42:36 +0200</lastBuildDate><atom:link href="https://michalkordyzon.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>A Quick Kafka Demo Visualisation</title><link>https://michalkordyzon.github.io/posts/a-quick-kafka-demo-visualisation/</link><pubDate>Sun, 02 Aug 2026 16:42:36 +0200</pubDate><guid>https://michalkordyzon.github.io/posts/a-quick-kafka-demo-visualisation/</guid><description>&lt;h2 id="visualise-kafka"&gt;Visualise Kafka&lt;/h2&gt;
&lt;p&gt;Some of my clients work with Kafka without ever developing an intuitive feel for its dynamics. Terms such as producers, consumers, partitions, offsets, lag, and consumer groups remain abstract until something breaks. To make these mechanics easier to understand, I built a small, intentionally playful simulation around a mission-control journey to the Moon. Kafka becomes the communication system coordinating the mission, while ASCII-based graphics show messages moving through the platform in real time. The humorous theme lowers the entry barrier, but the underlying goal is practical: to help people see how Kafka behaves, not merely memorize its terminology.&lt;/p&gt;</description></item><item><title>Memory layer for Agents with semi-graph knowledge</title><link>https://michalkordyzon.github.io/posts/memory-layer-for-agents-with-semi-graph-knowledge/</link><pubDate>Sat, 01 Aug 2026 16:42:36 +0200</pubDate><guid>https://michalkordyzon.github.io/posts/memory-layer-for-agents-with-semi-graph-knowledge/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Before jumping into retrieval, I wanted a memory layer that behaved less like a vector database and more like the way humans connect ideas.
So there is this idea to rather construct a semi-graph memory layer instead of storing isolated chunks, this layer combines semantic search with explicit relationships between concepts, people, facts, etc. The result is better, richer casuality that is visible in each answer of RAG system. In this post, I&amp;rsquo;ll walk through the architecture, the design decisions, and the lessons learned while building it.&lt;/p&gt;</description></item><item><title>Exploring Tiny Time-Mixer Model</title><link>https://michalkordyzon.github.io/posts/exploring-tiny-time-mixer-model/</link><pubDate>Fri, 28 Nov 2025 16:42:36 +0200</pubDate><guid>https://michalkordyzon.github.io/posts/exploring-tiny-time-mixer-model/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;2024 was a year where time series zero/few shot forecasting functioality made its way into LLM architectures: Moment, TimesFM, Chonos, Moirai, and many more showed up. Those were novel models but, computationally, heavy to use. So soon the second wave of lighter models appeared incluging Tiny Time-Mixer (TTM) architecture from IBM Research. TTM can work with just 1M parameters, it supports channel correlations and exogenous signals, and handles multivariate forecasting. Let&amp;rsquo;s dive in.&lt;/p&gt;</description></item><item><title>Granite Vision model notes</title><link>https://michalkordyzon.github.io/posts/granite-vision-model-notes/</link><pubDate>Tue, 26 Aug 2025 16:42:36 +0200</pubDate><guid>https://michalkordyzon.github.io/posts/granite-vision-model-notes/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Many VLMs perform great on benchmarks like viusal question-answering or multi-image reasoning. Models in 2024 were predominantly trained on natural images, thus often limiting performance in other domains like visual document undestanding.&lt;/p&gt;
&lt;p&gt;Granite Vision is a 3 billion parameters model focused on entreprise use cases with visual document understanding document content extraction and working with documents. Get the Granite Vision research paper &lt;a href="https://arxiv.org/abs/2502.09927"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="architecture"&gt;Architecture&lt;/h2&gt;
&lt;p&gt;Granite Vision was trained on 12 trillion tokens. Dataset for it&amp;rsquo;s training is constanlty curated by Granite Team but not open sourced. It contained 13 million images and 80 milllion instructions such as: document question-answering, scene understanding key-value extraction, text grounding, layout parsing, captioning, UI understanding, code comprehension.&lt;/p&gt;</description></item><item><title>SmolDocling model notes</title><link>https://michalkordyzon.github.io/posts/smoldocling-model-notes/</link><pubDate>Fri, 08 Aug 2025 16:42:36 +0200</pubDate><guid>https://michalkordyzon.github.io/posts/smoldocling-model-notes/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;OCR on documents remains a challenging task. While printed text can often be recognized with 95% or higher accuracy, real-world documents — containing handwriting, non-standard layouts, and other irregularities — are still much harder to read accurately. There are high quality systems solving documents reading in sub-tasks: OCR, layout analysis, structure recognition, classification.&lt;br&gt;
Recent trend is using large vision-language models to solve whole convertion task in one shot, and giving the user opportunity to define additional specific tasks to do in the prompt.
This post is about SmalDocling, a very tiny and compute-effient vision-language model doing the convertion task and the instruction task written into a prompt. The post is based on &lt;code&gt;SmolDocling&lt;/code&gt; &lt;a href="https://arxiv.org/abs/2503.11576"&gt;research paper&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>