<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Study on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/study/</link>
    <description>Recent content in Study on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 17 Jul 2008 18:44:00 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/study/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Programming: The invisible wall</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2008/programming-invisible-wall/</link>
      <pubDate>Thu, 17 Jul 2008 18:44:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2008/programming-invisible-wall/</guid>
      <description>In the past few weeks, as I&#39;ve tried and failed at various projects, there has been a realisation that you can only go so far with random reading and coding.&#xA;The first few years of programming are spent coding projects pretty minor on the algorithms/data structures side.&#xA;But when you finally start growing out of it and when &#39;cool&#39; projects for you start to become more complex, a seemingly invisible wall smacks you.</description>
    </item>
  </channel>
</rss>
