<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>coding-standards on Arrans Technical blog</title><link>https://arran4.github.io/blog/tags/coding-standards/</link><description>Recent content in coding-standards 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>Sun, 11 Oct 2026 02:42:55 +0000</lastBuildDate><atom:link href="https://arran4.github.io/blog/tags/coding-standards/index.xml" rel="self" type="application/rss+xml"/><item><title>Suggested Coding Standards for My Repositories and Coding Agents</title><link>https://arran4.github.io/blog/post/2026/055-suggested-coding-standards-for-repositories-and-agents/</link><pubDate>Sun, 11 Oct 2026 02:42:55 +0000</pubDate><author>technicalblog123@arran4.com (Arran Ubels)</author><guid>https://arran4.github.io/blog/post/2026/055-suggested-coding-standards-for-repositories-and-agents/</guid><description>I maintain several repositories with different languages, maturity levels and constraints. I do not want them all to adopt a generic architecture or an enormous rules file. I do want repeated decisions to become easier to review, and I want coding agents to stop rediscovering the same standards from scratch.
This is my suggested engineering baseline: a catalogue to select from, not a claim that every repository already complies. It collects the ideas in my existing posts and the recurring questions that arise when reviewing changes.</description></item></channel></rss>