<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Docka</title><link>https://docka.org/posts/</link><description>Recent content in Posts on Docka</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://docka.org/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>The human in the loop</title><link>https://docka.org/posts/2026-07-on-the-use-of-ai/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://docka.org/posts/2026-07-on-the-use-of-ai/</guid><description>&lt;p&gt;Let me start off by saying that I am not &amp;ldquo;Anti-AI&amp;rdquo;, AI is a useful tool that &lt;em&gt;&lt;strong&gt;can&lt;/strong&gt;&lt;/em&gt; greatly improve a developer&amp;rsquo;s speed.
This comes at a price, though, which I am not sure, I am willing to pay.&lt;/p&gt;
&lt;h2 id="your-brain-on-autopilot"&gt;Your brain on autopilot&lt;/h2&gt;
&lt;p&gt;I&amp;rsquo;ve tried it before; tab-completing entire functions feels awesome.
Having an LLM generate dozens of lines of wrapper functions that I would need minutes to write is extremely convenient.
Phrasing that commit message in a way that conforms to the guidelines as a non-native speaker is an enormous time-saver.
AI can be an incredibly useful tool, but let&amp;rsquo;s not kid ourselves: you&amp;rsquo;re not reading the code.
At most you&amp;rsquo;re skimming it and editing minor things.&lt;/p&gt;</description></item><item><title>So it begins</title><link>https://docka.org/posts/2026-07-so-it-begins/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://docka.org/posts/2026-07-so-it-begins/</guid><description>&lt;p&gt;This is the first of, hopefully, many updates.
In this series of posts, I hope to explain what&amp;rsquo;s happened over the last month of work at Docka.
Since this project is still in its early stages, these posts will probably be long but boring for now, since most of it is general architecture stuff.&lt;/p&gt;
&lt;h2 id="no-central-server-only-hosts"&gt;No central server, only hosts&lt;/h2&gt;
&lt;p&gt;Puppet and Salt both use a central server to distribute tasks or state to the nodes.
This has some undeniable advantages.
It opens up a whole lot of options, like centralized reporting and ensuring all nodes apply the same state, but, as usual, this comes at a cost.
One downside is that this acts as a single point of failure.
While the server is down, at most, the nodes can apply their old state, and reports can&amp;rsquo;t be collected during this time.&lt;/p&gt;</description></item></channel></rss>