<?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>Thoughts and Code</title><link>https://www.hamnis.org/</link><description>Recent content on Thoughts and Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Mar 2026 20:00:00 +0100</lastBuildDate><atom:link href="https://www.hamnis.org/index.xml" rel="self" type="application/rss+xml"/><item><title>Maven Credential Helper</title><link>https://www.hamnis.org/posts/2026-maven-credential-helper/</link><pubDate>Mon, 02 Mar 2026 20:00:00 +0100</pubDate><guid>https://www.hamnis.org/posts/2026-maven-credential-helper/</guid><description>&lt;p&gt;As a longtime Maven user, I have quite often been annoyed by one particular feature: Repository authentication.
Since the beginning of Maven 2, this has been done the same way, by having a &lt;code&gt;&amp;lt;server&amp;gt;&lt;/code&gt; node in the &lt;a href="https://maven.apache.org/settings.html#Servers"&gt;&lt;code&gt;$HOME/.m2/settings.xml&lt;/code&gt;&lt;/a&gt;.
This post will explore a new &lt;a href="https://codeberg.org/hamnis/maven-credential-helper"&gt;Maven extension&lt;/a&gt; I have created that attempts to avoid hard-coding these credentials in a static xml file.
Before we get into that, however, we will take a look at how this works today.&lt;/p&gt;</description></item><item><title>with a little --help from my friends</title><link>https://www.hamnis.org/posts/2025-a-little-help-from-my-friends/</link><pubDate>Fri, 05 Dec 2025 11:29:58 +0100</pubDate><guid>https://www.hamnis.org/posts/2025-a-little-help-from-my-friends/</guid><description>&lt;h2 id="working-with-the-command-line"&gt;Working with the command line&lt;/h2&gt;
&lt;p&gt;I have been a developer for quite a few years now, and I have been using Linux for most of the time.
Being a Linux user I am not afraid of using the command line, in fact, a lot of the time is spent using the terminal.
Over the years I’ve spent a lot of time in the terminal, and there’s still a lot of things I don’t remember by heart.&lt;/p&gt;</description></item><item><title>Deno scripting</title><link>https://www.hamnis.org/posts/2025-deno-scripting/</link><pubDate>Thu, 13 Feb 2025 00:00:00 +0000</pubDate><guid>https://www.hamnis.org/posts/2025-deno-scripting/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Have you ever felt like you’re making too many shell scripts? Some may say that every line of &lt;code&gt;bash&lt;/code&gt; is too much &lt;code&gt;bash&lt;/code&gt;.
An example of why bash may be not the best solution for writing scripts is shellcheck. There are &lt;a href="https://gist.github.com/eggplants/9fbe03453c3f3fd03295e88def6a1324"&gt;too many possible mistakes&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In the last few years I have been experimenting with different scripting languages, and I think I have found a few good ones.&lt;/p&gt;
&lt;p&gt;A non-exhaustive list is:&lt;/p&gt;</description></item></channel></rss>