<?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>Hancic Tech Blog</title><link>https://en.hancic.site/</link><description>Recent content on Hancic Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://en.hancic.site/index.xml" rel="self" type="application/rss+xml"/><item><title>About</title><link>https://en.hancic.site/about/</link><pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate><guid>https://en.hancic.site/about/</guid><description>&lt;p&gt;Hi, I&amp;rsquo;m &lt;strong&gt;Hancic&lt;/strong&gt; — a full-stack software engineer based in Beijing, China.&lt;/p&gt;
&lt;h2 id="what-i-do"&gt;What I do&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Backend / data / operations&lt;/strong&gt;, with Python and Rust as my main languages&lt;/li&gt;
&lt;li&gt;Write mostly in an &lt;strong&gt;AI-driven, practical&lt;/strong&gt; way — comfortable across tooling and stacks&lt;/li&gt;
&lt;li&gt;Interested in &lt;strong&gt;distributed systems&lt;/strong&gt;, &lt;strong&gt;trading systems / quant&lt;/strong&gt;, and &lt;strong&gt;self-hosting&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="this-blog"&gt;This blog&lt;/h2&gt;
&lt;p&gt;Engineering notes in English for a global audience: systems design, infrastructure,
and the occasional opinion on tooling. The Chinese blog lives at
&lt;a href="https://blog.hancic.site"&gt;blog.hancic.site&lt;/a&gt; and covers similar topics in Chinese.&lt;/p&gt;</description></item><item><title>Welcome to This Blog</title><link>https://en.hancic.site/welcome/</link><pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate><guid>https://en.hancic.site/welcome/</guid><description>&lt;p&gt;This is the first post on the English side of hancic.site.&lt;/p&gt;
&lt;h2 id="why-another-blog"&gt;Why another blog&lt;/h2&gt;
&lt;p&gt;The Chinese blog at &lt;a href="https://blog.hancic.site"&gt;blog.hancic.site&lt;/a&gt; has been running for a while.
Some of the topics — distributed systems, trading systems, and engineering practice —
are interesting to a global audience too. So here we are: an English blog, written
without a translation step.&lt;/p&gt;
&lt;h2 id="what-to-expect"&gt;What to expect&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Systems engineering and architecture notes&lt;/li&gt;
&lt;li&gt;Trading systems and quant tooling&lt;/li&gt;
&lt;li&gt;Occasional tooling and self-hosting stories&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="comments"&gt;Comments&lt;/h2&gt;
&lt;p&gt;Comments run on &lt;a href="https://giscus.app"&gt;giscus&lt;/a&gt;, powered by GitHub Discussions —
feel free to drop a note below!&lt;/p&gt;</description></item><item><title>Where Distributed Systems Complexity Comes From</title><link>https://en.hancic.site/distributed-systems-complexity/</link><pubDate>Fri, 11 Sep 2026 00:00:00 +0000</pubDate><guid>https://en.hancic.site/distributed-systems-complexity/</guid><description>The complexity of distributed systems reduces to three root problems: space, time, and consensus. Why each one resists a simple answer, how they stack, and what that means when you pick a protocol.</description></item></channel></rss>