<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Kai's Site</title>
        <link>https://example.com/</link>
        <description>A data-focused portfolio for financial analytics, data engineering, machine learning, and product-minded projects.</description>
        <lastBuildDate>Wed, 20 May 2026 11:16:27 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en-US</language>
        <copyright>Copyright (c) 2026-present Kai</copyright>
        <item>
            <title><![CDATA[How I Work with Risk Data]]></title>
            <link>https://example.com/en/thinking/posts/how-i-work-with-risk-data</link>
            <guid isPermaLink="false">https://example.com/en/thinking/posts/how-i-work-with-risk-data</guid>
            <pubDate>Thu, 01 Jan 1970 00:00:00 GMT</pubDate>
            <description><![CDATA[A short note on turning risk data into practical monitoring and decisions.]]></description>
            <content:encoded><![CDATA[<h1 id="how-i-work-with-risk-data" tabindex="-1">How I Work with Risk Data <a class="header-anchor" href="#how-i-work-with-risk-data" aria-label="Permalink to &quot;How I Work with Risk Data&quot;"></a></h1>
<p>Risk data is rarely tidy at the beginning. It usually arrives through business processes, policy definitions, systems history, and operational shortcuts. My first step is to understand what the data represents in the real world before treating it as a modeling problem.</p>
<p>Good risk analytics should make decisions easier to inspect. That means clear definitions, repeatable checks, sensible thresholds, and enough context for a reviewer to understand why something was flagged.</p>
<p>The best analytical systems are not just accurate. They are usable, explainable, and maintainable by the people who rely on them.</p>
]]></content:encoded>
            <author>Kai</author>
        </item>
    </channel>
</rss>