<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Joel Spolsky on Bruno Pedro</title><link>https://brunopedro.com/tags/joel-spolsky/</link><description>Recent content in Joel Spolsky on Bruno Pedro</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 May 2018 10:00:15 -0700</lastBuildDate><atom:link href="https://brunopedro.com/tags/joel-spolsky/index.xml" rel="self" type="application/rss+xml"/><item><title>Why refactoring?</title><link>https://brunopedro.com/2012/12/18/why-refactoring/</link><pubDate>Tue, 18 Dec 2012 12:43:47 +0000</pubDate><guid>https://brunopedro.com/2012/12/18/why-refactoring/</guid><description>&lt;p>Interesting thoughts about refactoring, starting with a comprehensive post by &lt;a href="http://www.blogger.com/profile/17371102366836131341" title="Jim Bird">Jim Bird&lt;/a>, stating what &lt;strong>is not refactoring&lt;/strong>:&lt;/p>
&lt;blockquote>
&lt;p>Fixing any bugs that you find along the way is not refactoring. Optimization is not refactoring. Tightening up error handling and adding defensive code is not refactoring. Making the code more testable is not refactoring – although this may happen as the result of refactoring. All of these are good things to do. But they aren&amp;rsquo;t refactoring. &amp;ndash; &lt;em>in &lt;a href="http://swreflections.blogspot.co.uk/2012/04/what-refactoring-is-and-what-it-isnt.html" title="What Refactoring is, and what it isn’t">What Refactoring is, and what it isn&amp;rsquo;t&lt;/a>&lt;/em>&lt;/p></description></item></channel></rss>