<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Practice on Scholion</title><link>https://scholion.thluiz.com/tags/software-practice/</link><description>Recent content in Software-Practice on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Wed, 18 Nov 2026 13:08:13 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/software-practice/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Write a Good Piece of Code</title><link>https://scholion.thluiz.com/notes/how-to-write-a-good-piece-of-code/</link><pubDate>Wed, 26 Jun 2019 11:05:46 +0000</pubDate><guid>https://scholion.thluiz.com/notes/how-to-write-a-good-piece-of-code/</guid><description>The article argues that good code starts before implementation, with validation, decomposition, tests, consistency, review, and shipping. It also says the process should stay practical and avoid overengineering.</description></item><item><title>How Do I Write Good Code?</title><link>https://scholion.thluiz.com/notes/how-do-i-write-good-code/</link><pubDate>Mon, 08 Aug 2016 17:00:31 +0000</pubDate><guid>https://scholion.thluiz.com/notes/how-do-i-write-good-code/</guid><description>The post ranks five priorities for good code: make it easy to change, readable, working, elegant, and shaped by advice from experienced practitioners.</description></item><item><title>The traits of a proficient programmer</title><link>https://scholion.thluiz.com/notes/the-traits-of-a-proficient-programmer/</link><pubDate>Mon, 01 Aug 2016 12:09:28 +0000</pubDate><guid>https://scholion.thluiz.com/notes/the-traits-of-a-proficient-programmer/</guid><description>The article distinguishes competence from proficiency in programming, arguing that proficiency means understanding why something works and when to use it, not just knowing how to do it.</description></item></channel></rss>