<?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: kvgc</title>
    <description>The latest articles on DEV Community by kvgc (@kvgc).</description>
    <link>https://dev.to/kvgc</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%2F835139%2F626fe00c-a688-4308-8b45-6c3eb0f30c75.jpeg</url>
      <title>DEV Community: kvgc</title>
      <link>https://dev.to/kvgc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kvgc"/>
    <language>en</language>
    <item>
      <title>Strategies to understand codebase ?</title>
      <dc:creator>kvgc</dc:creator>
      <pubDate>Thu, 24 Mar 2022 21:24:04 +0000</pubDate>
      <link>https://dev.to/kvgc/strategies-to-understand-codebase--3m6b</link>
      <guid>https://dev.to/kvgc/strategies-to-understand-codebase--3m6b</guid>
      <description>&lt;p&gt;The ability to understand a codebase is really helpful when one is trying to make tweaks/develop the underlying code.  Ideally, repos have good documentation to guide the interested developer but for the most part, this may not necessarily exist.&lt;/p&gt;

&lt;p&gt;Therefore, given a GitHub repo, what's a good strategy to understand &lt;em&gt;(in broad strokes)&lt;/em&gt; the structure of the code? &lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
