<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Guide on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/guide/</link>
    <description>Recent content in Guide on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 23 Mar 2011 13:46:00 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/guide/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Code reading and Bug fixing 101</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/code-reading-and-bug-fixing-101/</link>
      <pubDate>Wed, 23 Mar 2011 13:46:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2011/code-reading-and-bug-fixing-101/</guid>
      <description>Summer is here, and Google Summer of Code is on its way. The biggest hurdle new contributors often face (after compiling trunk ;)) is to get their head around the project they would like to work on, understanding how it works, where the parts fit in, and how to fix bugs or make improvements. Speaking from my experience, it took me the better part of a month to understand how KWin worked before I could actually hack on it for Season on KDE.</description>
    </item>
  </channel>
</rss>
