https://arran4.github.io/blog/categories/go/Recent content in go on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Fri, 10 Jul 2026 13:32:59 +1000https://arran4.github.io/blog/post/2026/016-go-error-handling/Fri, 10 Jul 2026 13:32:59 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/016-go-error-handling/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&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&rsquo;s dive into how I handle errors effectively.https://arran4.github.io/blog/post/2026/013-resolving-golangci-lint-go-version-conflicts/Tue, 07 Jul 2026 21:49:40 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/013-resolving-golangci-lint-go-version-conflicts/If you have encountered a build failure in your Go project&rsquo;s GitHub Actions pipeline, you might see an error output similar to this: 1run golangci-lint 2 3 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint config path] in [/home/runner/work/go-pattern/go-pattern] ... 4 5 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint run] in [/home/runner/work/go-pattern/go-pattern] ... 6 7 Error: can&#39;t load config: the Go language version (go1.24) used to build golangci-lint is lower than the targeted Go version (1.25.0) 8 9 Failed executing command with error: can&#39;t load config: the Go language version (go1.