<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Akande Bolatito</title>
    <description>The latest articles on DEV Community by Akande Bolatito (@akande_bolatito_43b2efc1d).</description>
    <link>https://dev.to/akande_bolatito_43b2efc1d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1000418%2Ff8e50505-8047-490c-b77b-dc9d5671d036.png</url>
      <title>DEV Community: Akande Bolatito</title>
      <link>https://dev.to/akande_bolatito_43b2efc1d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akande_bolatito_43b2efc1d"/>
    <language>en</language>
    <item>
      <title>How long does code refactoring takes</title>
      <dc:creator>Akande Bolatito</dc:creator>
      <pubDate>Thu, 05 Jan 2023 04:29:40 +0000</pubDate>
      <link>https://dev.to/akande_bolatito_43b2efc1d/how-long-does-code-refactoring-takes-4j0n</link>
      <guid>https://dev.to/akande_bolatito_43b2efc1d/how-long-does-code-refactoring-takes-4j0n</guid>
      <description>&lt;p&gt;in practice, most times you look at your code and you're happy with it or there's a small refactor, like extracting a method, which takes a minute or two of your time. On rare occasions, a significant refactoring becomes apparent and takes up 20 – 30 minutes of your time&lt;/p&gt;

</description>
      <category>emptystring</category>
    </item>
    <item>
      <title>what is the most common cause of refactoring problems?</title>
      <dc:creator>Akande Bolatito</dc:creator>
      <pubDate>Thu, 05 Jan 2023 04:27:38 +0000</pubDate>
      <link>https://dev.to/akande_bolatito_43b2efc1d/what-is-the-most-common-cause-of-refactoring-problems-3klb</link>
      <guid>https://dev.to/akande_bolatito_43b2efc1d/what-is-the-most-common-cause-of-refactoring-problems-3klb</guid>
      <description>&lt;p&gt;The most common cause of refactoring problems is not in the code -- it's a lack of proper tools. Refactoring nearly always includes renaming variables and methods, changing method signatures, and moving things around. Trying to make all these changes by hand can easily lead to disaster.&lt;/p&gt;

</description>
      <category>learning</category>
      <category>programming</category>
    </item>
    <item>
      <title>Reasons why you should go into code refactoring today!</title>
      <dc:creator>Akande Bolatito</dc:creator>
      <pubDate>Tue, 03 Jan 2023 08:31:13 +0000</pubDate>
      <link>https://dev.to/akande_bolatito_43b2efc1d/reasons-why-you-should-go-into-code-refactoring-today-4lp1</link>
      <guid>https://dev.to/akande_bolatito_43b2efc1d/reasons-why-you-should-go-into-code-refactoring-today-4lp1</guid>
      <description>&lt;p&gt;When you hear the word code refactoring what comes to mind? &lt;br&gt;
Well think of a car that was manufactured in the 90’s and is transformed to a comfy and smooth, and also great looking lambo that’s just an illustration😂. Refactoring is a systematic process of improving code without creating new functionality that can transform a mess into clean code and simple design.one of the main reason of doing code refactoring is to eliminate dirty code which might be as a result of rushing or short cuts in the code creation process anyways see code refactoring as a way of restructuring the whole process, making the code simple to read, understand and give higher efficiency. So tell me will you stick to The car created in the 90’s or you will preface a Lamborghini truck?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>discuss</category>
      <category>news</category>
      <category>watercooler</category>
    </item>
  </channel>
</rss>
