<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Development on Arrans Technical blog</title><link>https://arran4.github.io/blog/categories/software-development/</link><description>Recent content in Software Development on Arrans Technical blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>technicalblog123@arran4.com (Arran Ubels)</managingEditor><webMaster>technicalblog123@arran4.com (Arran Ubels)</webMaster><copyright>Arran Ubels. This work is licensed under a &lt;a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License&lt;/a>.</copyright><lastBuildDate>Fri, 10 Jul 2026 13:32:59 +1000</lastBuildDate><atom:link href="https://arran4.github.io/blog/categories/software-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Effective Error Handling in Go: Wrapping, Sentinels, and Custom Types</title><link>https://arran4.github.io/blog/post/2026/016-go-error-handling/</link><pubDate>Fri, 10 Jul 2026 13:32:59 +1000</pubDate><author>technicalblog123@arran4.com (Arran Ubels)</author><guid>https://arran4.github.io/blog/post/2026/016-go-error-handling/</guid><description>Error handling in Go is straightforward, explicit, and forces developers to deal with failure states right at the point of origin. While if err != nil is a running joke in the community, when used correctly, Go&amp;rsquo;s error handling produces robust, debuggable, and maintainable software.
In my Go projects, I adhere to a set of practices that ensure errors are not just checked, but are rich with context and actionable. Let&amp;rsquo;s dive into how I handle errors effectively.</description></item><item><title>LLM Instructions: Upgrading Projects</title><link>https://arran4.github.io/blog/post/2026/014-llm-upgrade-instructions/</link><pubDate>Wed, 08 Jul 2026 11:33:21 +1000</pubDate><author>technicalblog123@arran4.com (Arran Ubels)</author><guid>https://arran4.github.io/blog/post/2026/014-llm-upgrade-instructions/</guid><description>This post acts as explicit instructions and rules for LLMs tasked with upgrading software projects. When applying an upgrade, you must follow these rules meticulously to ensure the project remains stable and up-to-date.
Upgrade Rules When upgrading a repository, always target the latest versions of the following technologies:
Flutter &amp;amp; Dart: Ensure the project uses the latest stable releases. GitHub Actions: Upgrade all actions to their latest major versions. Go (Golang): Update to the latest stable Go release.</description></item></channel></rss>