<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technology on rdner's blog</title><link>https://rdner.de/posts/tech/</link><description>Recent content in Technology on rdner's blog</description><generator>Hugo</generator><language>en-US</language><managingEditor>denis@rdner.de (Denis Rechkunov)</managingEditor><webMaster>denis@rdner.de (Denis Rechkunov)</webMaster><copyright>Denis Rechkunov</copyright><lastBuildDate>Tue, 31 Mar 2026 10:25:00 +0200</lastBuildDate><atom:link href="https://rdner.de/posts/tech/index.xml" rel="self" type="application/rss+xml"/><item><title>Private AI: Self-hosting an AI Chatbot on Your Local Network</title><link>https://rdner.de/posts/tech/self-hosted-ai-chatbot/</link><pubDate>Tue, 31 Mar 2026 10:25:00 +0200</pubDate><author>denis@rdner.de (Denis Rechkunov)</author><guid>https://rdner.de/posts/tech/self-hosted-ai-chatbot/</guid><description>&lt;p&gt;I&amp;rsquo;m a firm believer that the future of 
&lt;a href="https://en.wikipedia.org/wiki/Artificial_intelligence" rel="nofollow noreferrer" target="_blank"&gt;AI&lt;/a&gt; is private deployments. By concentrating so much power in the hands of a few corporations we will inevitably find ourselves in a dystopian future.&lt;/p&gt;
&lt;p&gt;Some time ago I started to wonder: what would it take to self-host my own &amp;ldquo;Claude&amp;rdquo; or &amp;ldquo;ChatGPT&amp;rdquo;?&lt;/p&gt;
&lt;p&gt;Most of the time I use 
&lt;a href="https://en.wikipedia.org/wiki/Large_language_model" rel="nofollow noreferrer" target="_blank"&gt;LLM&lt;/a&gt; chatbots as a very advanced search engine. But what I actually need it for is to help me navigate numerous documents written in legal German (as if regular German weren&amp;rsquo;t difficult enough, people invented the legal version of it). Obviously, the problem here is privacy. Under no circumstances can I trust my personal documents to a third-party.&lt;/p&gt;</description></item><item><title>Code Maintainability Is Not Always a Technical Problem</title><link>https://rdner.de/posts/tech/code-maintainability-is-not-always-a-technical-problem/</link><pubDate>Sat, 05 Jul 2025 18:19:58 +0200</pubDate><author>denis@rdner.de (Denis Rechkunov)</author><guid>https://rdner.de/posts/tech/code-maintainability-is-not-always-a-technical-problem/</guid><description>&lt;h2 id="context"&gt;
 Context&amp;nbsp;&lt;a class="undecorated heading-anchor" href="#context"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;First, who am I to even talk about it? What is my background?&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been building software for the last 15 years. I&amp;rsquo;ve worked at 8 companies ranging from small startups to one of the biggest tech companies in the world.&lt;/p&gt;
&lt;p&gt;At the moment I primarily work on 
&lt;a href="https://github.com/elastic/beats" rel="nofollow noreferrer" target="_blank" title="Elastic Beats"&gt;Beats&lt;/a&gt;. A few facts about this repository (July 2025):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;~15 teams work on it&lt;/li&gt;
&lt;li&gt;918 unique contributors (including external ones)&lt;/li&gt;
&lt;li&gt;4,183 Go files&lt;/li&gt;
&lt;li&gt;653,168 lines of code&lt;/li&gt;
&lt;li&gt;45,205 pull requests&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So, it&amp;rsquo;s a relatively big project with quite a few people working on it. Let&amp;rsquo;s take my path from onboarding to the present day as an example for this article.&lt;/p&gt;</description></item></channel></rss>