<?xml version="1.0" encoding="UTF-8"?>
<post>
  <body>&lt;p&gt;How much time do you spend reading about Ruby and Rails, instead of actually doing something? Wich is coding, by the way :)&lt;/p&gt;

&lt;p&gt;If I read/watch/listen_to material on Rails during three hours, and I only code for one hour, I think I'm not being productive in my path to be a great Web developer. Anyway, 1/3 of my learning time is being spent on non-coding things.&lt;/p&gt;

&lt;p&gt;I realized my time is much more productive if I follow some basic rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reading RSS once a week: it's very easy to become so fascinated about the new stuff coming every day on the Ruby on Rails world. Not reading RSS everyday gives me 2 benefits: I don't get overwhelmed and frustrated about what I don't know yet (what is not a great motivator), and I save time to actually code;&lt;/li&gt;
&lt;li&gt;Sticking to a subject: I'm now studying RSpec and BDD. I'm studying the necessary to be comfortable at the subject;&lt;/li&gt;
&lt;li&gt;Studying in layers: after some rounds of subjecs I studied, I may get back to subjects I need to gain a deeper understanding. Like, at first I may study a little on BDD/RSpec and sometime later I'll catch up on more advanced topics.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And also, while reading or watching a screencast you can always code along with the material pausing and resuming all the time (which is good, because for me it counts as coding).&lt;/p&gt;</body>
  <comments-count type="integer">8</comments-count>
  <created-at type="datetime">2008-11-26T16:16:36Z</created-at>
  <id type="integer">6</id>
  <permalink nil="true"></permalink>
  <slug>the-do-read-ration</slug>
  <title>The Do-to-Read Ratio</title>
  <updated-at type="datetime">2008-11-27T10:14:07Z</updated-at>
  <user-id type="integer" nil="true"></user-id>
</post>
