https://arran4.github.io/blog/tags/best-practices/Recent content in best-practices 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>.Mon, 13 Jul 2026 13:33:09 +1000https://arran4.github.io/blog/post/2026/022-llm-expand-regex-test/Mon, 13 Jul 2026 13:33:09 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/022-llm-expand-regex-test/When generating code, Large Language Models (LLMs) often default to using Regular Expressions (regex) for string parsing and validation tasks. While regex is a powerful tool for human developers aiming for concise code, it is rarely the optimal choice for LLMs writing production-grade software. Instead of always defaulting to dense regular expressions, LLMs should often expand logic into explicit, step-by-step procedural code and accompany that code with comprehensive, table-driven unit tests.https://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.