Levy Carneiro

These days I had to find if there was any broken link (error 404) in a group of sites.

I found this to be very useful:

wget –recursive –spider http://levycarneiro.com

This command will download everything from the URL, and generate a report like this:

Found 13 broken links.

http://levycarneiro.com/levy@levycarneiro.com referred by:
http://levycarneiro.com/
http://levycarneiro.com/images/posts/Multiple_models_one_form_NewProject.jpg referred by:
http://levycarneiro.com/category/ruby-on-rails/
http://levycarneiro.com/tag/twitter/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/twitter/
http://levycarneiro.com/tag/rails/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/rails/
http://levycarneiro.com/tag/portfolio/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/portfolio/
http://levycarneiro.com/2009/04/transito-nao-an-experiment-with-twitter-traffic-jams-and-ruby-on-rails/levy@levycarneiro.com referred by:
http://levycarneiro.com/2009/04/transito-nao-an-experiment-with-twitter-traffic-jams-and-ruby-on-rails/
http://levycarneiro.com/tag/traffic/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/traffic/
http://levycarneiro.com/tag/projects/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/projects/
http://levycarneiro.com/category/projects/levy@levycarneiro.com referred by:
http://levycarneiro.com/category/projects/
http://levycarneiro.com/tag/ruby/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/ruby/
http://levycarneiro.com/category/ruby-on-rails/levy@levycarneiro.com referred by:
http://levycarneiro.com/category/ruby-on-rails/
http://levycarneiro.com/category/twitter/levy@levycarneiro.com referred by:
http://levycarneiro.com/category/twitter/
http://levycarneiro.com/tag/ruby-on-rails/levy@levycarneiro.com referred by:
http://levycarneiro.com/tag/ruby-on-rails/

I’ve got some work to do then

How much time do you spend reading about Ruby and Rails, instead of actually doing something? Wich is coding, by the way

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.

I realized my time is much more productive if I follow some basic rules:

• 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;
• Sticking to a subject: I’m now studying RSpec and BDD. I’m studying the necessary to be comfortable at the subject;
• 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.

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).