<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Clarity on Scholion</title><link>https://scholion.thluiz.com/tags/code-clarity/</link><description>Recent content in Code-Clarity on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 06 Oct 2026 04:20:06 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/code-clarity/index.xml" rel="self" type="application/rss+xml"/><item><title>The thing with code clarity: you can't be proud of something I can't read</title><link>https://scholion.thluiz.com/notes/the-thing-with-code-clarity-you-cant-be-proud-of-something-i/</link><pubDate>Fri, 24 Apr 2015 10:32:54 -0300</pubDate><guid>https://scholion.thluiz.com/notes/the-thing-with-code-clarity-you-cant-be-proud-of-something-i/</guid><description>The post argues that code clarity matters because code must communicate to people as well as computers, and that readable, maintainable code comes from naming, structure, spacing, comments, and refactoring.</description></item></channel></rss>