<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Conventional Commits on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/conventional-commits/</link><description>Recent content in Conventional Commits on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 18:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/conventional-commits/index.xml" rel="self" type="application/rss+xml"/><item><title>The Conventions I Follow</title><link>https://lab.artur-rios.tech/engineering/my-conventions/</link><pubDate>Wed, 21 Oct 2026 18:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/engineering/my-conventions/</guid><description>&lt;p&gt;A convention is a decision made once. Without them, every new repository,&#10;class and commit reopens the same small questions: what to call it, where to&#10;put it, how to phrase it. None of those questions is hard, but answering them&#10;again every time is slow, and answering them differently every time leaves a&#10;codebase that reads like it was written by several people who never met.&lt;/p&gt;&#10;&lt;p&gt;This page collects the conventions I follow in my own projects. Where a style&#10;guide already covers something, I follow it; the&#10;&lt;a href="https://google.github.io/styleguide/"&gt;Google Style Guides&lt;/a&gt; are my default&#10;reference for the languages they cover. What is written here is either what&#10;those guides leave open, or a choice I have made on top of them.&lt;/p&gt;</description></item></channel></rss>