https://arran4.github.io/blog/tags/llm/Recent content in llm 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/019-llm-compliance-version-upgrades/Sat, 11 Jul 2026 13:21:18 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/019-llm-compliance-version-upgrades/When instructing LLM agents (like coding assistants) to update dependencies such as golangci-lint, there are often issues with the models defaulting to older, outdated versions based on their training data. If you try to correct them, they may fall back on what they &ldquo;know&rdquo; rather than following your instructions, resulting in version downgrades, overly specific version pinning, and regressions. This post establishes strict rules and alternative strategies to ensure compliance and prevent these downgrades.https://arran4.github.io/blog/post/2026/017-repoless-explanation-golangci-lint/Fri, 10 Jul 2026 15:57:37 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/017-repoless-explanation-golangci-lint/When encountering the following golangci-lint error in GitHub Actions or locally: 1run golangci-lint 2 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint config path] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 3 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint run] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 4 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) 5 Failed executing command with 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.https://arran4.github.io/blog/post/2026/015-llm-instructions-golangci-lint-version-conflicts/Fri, 10 Jul 2026 13:32:21 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/015-llm-instructions-golangci-lint-version-conflicts/This post serves as explicit instructions for LLM agents (like Jules) on how to correctly handle and resolve golangci-lint Go version mismatch errors without requiring the user to repeatedly copy-paste the same workflow. If you encounter an error like the following during a build or lint process: 1run golangci-lint 2 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint config path] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 3 Running [/home/runner/golangci-lint-1.64.8-linux-amd64/golangci-lint run] in [/home/runner/work/fork-mdtohtml/fork-mdtohtml] ... 4 Error: can&#39;t load config: the Go language version (go1.https://arran4.github.io/blog/post/2026/014-llm-upgrade-instructions/Wed, 08 Jul 2026 11:33:21 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/014-llm-upgrade-instructions/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; 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.