<?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: TaylorEdwards</title>
    <description>The latest articles on DEV Community by TaylorEdwards (@tayloredwards).</description>
    <link>https://dev.to/tayloredwards</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%2F72986%2F6e283257-bb04-4148-ba70-5823f305a327.jpeg</url>
      <title>DEV Community: TaylorEdwards</title>
      <link>https://dev.to/tayloredwards</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tayloredwards"/>
    <language>en</language>
    <item>
      <title>What Makes an Effective Code Walk Through?</title>
      <dc:creator>TaylorEdwards</dc:creator>
      <pubDate>Mon, 14 Jan 2019 17:49:19 +0000</pubDate>
      <link>https://dev.to/tayloredwards/what-makes-an-effective-code-walk-through-242j</link>
      <guid>https://dev.to/tayloredwards/what-makes-an-effective-code-walk-through-242j</guid>
      <description>&lt;h2&gt;
  
  
  Hi All!
&lt;/h2&gt;

&lt;p&gt;First dev.to post, this is exciting!&lt;/p&gt;

&lt;p&gt;Throughout my very brief software development career, I've been onboarded to various projects. Each one of these onboarding sessions had a code walkthrough of some sort. There were slide decks, handouts, and an endless sea of confluence pages. These methods (and various combinations), all have their pros and cons, but I can't help but think there must be a better way to go about this.&lt;/p&gt;

&lt;h2&gt;
  
  
  Question
&lt;/h2&gt;

&lt;p&gt;What types of code walk through sessions have you found to be particularly effective and why?&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>help</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
