<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clean Code on Goncalo Pereira</title><link>https://goncalopereira.com/tags/clean-code/</link><description>Recent content in Clean Code on Goncalo Pereira</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Mon, 15 Jun 2026 14:03:26 +0100</lastBuildDate><atom:link href="https://goncalopereira.com/tags/clean-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Development Quality for Ruby and Chef (DevOps Weekly #298)</title><link>https://goncalopereira.com/archive/2016-09-06_development-quality-for-ruby-and-chef/</link><pubDate>Tue, 06 Sep 2016 11:30:19 +0000</pubDate><guid>https://goncalopereira.com/archive/2016-09-06_development-quality-for-ruby-and-chef/</guid><description>&lt;p&gt;originally posted &lt;a href="https://medium.com/blog-goncalopereira-com/development-quality-for-ruby-and-chef-59ed7a3e94dc"&gt;medium&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A few years ago I wrote a small blog post about how to setup a local development environment for Chef using Vagrant and Test-Kitchen (you can see it &lt;a href="https://medium.com/@pereiragoncalo/setting-up-for-infrastructure-development-1ab67b721ff9#.3wc9qvfvs"&gt;here&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Lately I’ve been questioned about how to maintain a codebase through the years and how to work on/find quality metrics.&lt;/p&gt;
&lt;p&gt;A lot of people come from previous background where just vi/nano is required to lash out some code and moving to Ruby/Chef it seems only the language changed but there wasn’t much investment on better software development practices.&lt;/p&gt;</description></item></channel></rss>