<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Writing code is life</title><link>https://arkord.de/tags/tools/</link><description>Recent content in Tools on Writing code is life</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Mar 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://arkord.de/tags/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub migration tools reimagined</title><link>https://arkord.de/posts/github-migration-tools-reimagined/</link><pubDate>Tue, 17 Mar 2026 08:00:00 +0200</pubDate><guid>https://arkord.de/posts/github-migration-tools-reimagined/</guid><description>&lt;p&gt;In the last post I wrote about the &lt;a href="https://arkord.de/posts/state-of-github-migration-tools/"&gt;&amp;ldquo;State of GitHub migration tools&amp;rdquo;&lt;/a&gt;. I this post I would like to present my humble attempt to unify and improve the developer experience regarding the GitHub migration tools.&lt;/p&gt;</description></item><item><title>State of GitHub migration tools</title><link>https://arkord.de/posts/state-of-github-migration-tools/</link><pubDate>Mon, 16 Mar 2026 18:00:00 +0200</pubDate><guid>https://arkord.de/posts/state-of-github-migration-tools/</guid><description>&lt;p&gt;For some time I am working on migration projects from various platforms to GitHub. What I soon realized is the miserable state of the GitHub migration tools. It is easy to complain when you&amp;rsquo;re not involved in the development process and don&amp;rsquo;t know the priorities and decisions. Therefore, I would like to outline the current state of the migration tools and what we maybe can do better.&lt;/p&gt;</description></item></channel></rss>