incubate!(bang) has officially started back up - check incubatebang.com for details

isotope|eleven


About_robby_clements

Robby Clements

developer

Robby Clements is a Ruby on Rails developer for isotope|eleven. Before he joined us, he served in the U.S. Navy. He has 2 years of professional developing experience and 5+ years experience in Computer Networking. He also has great hair.

Blog Posts

I found this article today and thought I'd share. I figured it to be the best description of how I learned RoR. It describes some of the pitfalls a beginner can fall into when first learning.

http://rob.yurkowski.net/post/17610425880/rails-is-definitely-not-for-beginners

Although I must say I disagree with what some of this article says because the great thing about Rails and how far the community has come, is how much easier things are these days with all the gems we have and how extensive most of the documentation is. Just some things to think about.

Now, I'm getting verklempt! Talk amongst yourselves. I'll give you a topic. The Prince of Tides was about neither a prince nor tides.

About_robby_clements

Learn to Program

by: Robby Clements

January 21st, 2012 23:35

I started learning ruby with "Learn to Program" written by Chris Pine. It is a great book and kept me coming back for more. Another book that most mock and for good reason is "Why's Poignant Guide to Ruby", but it is the book that made me want to become a rubyist in the first place. I believe it to be mostly for fun but it was very clutch in attracting me to this community.  Plenty of amazing sites are out there to help you along the way as well as the extensive Ruby community. A few sites I would recommend would be:

www.rubymonk.com
www.rubylearning.org
www.rubyquiz.com
www.teachmetocode.com
www.railsforzombies.org
www.ruby.railstutorial.org/ruby-on-rails-tutorial-book
www.tutorials.jumpstartlab.com

I also found this blog post at astonj.com which is a more extensive look into planning your learning path.
http://astonj.com/tech/best-way-to-learn-ruby-rails/

That should be more than enough to get you started.

GLHF
 

Lately I have been noticing many people who ask how they can better themselves and their code. I too ask myself this everyday, as we all should. So I have decided to touch on the subject to get you started and pointed in the right direction.

One of the best things I have found is whenever you find yourself in need of reading material, read documentation. Just start with Array, Hash, and Enumerable. Understanding those will put you leaps and bounds from where you stand without a good grasp on the basics. You don't have to memorize these, that is what they are there for. You just need to read through them every once in a while and let the concept of each sink in. Also, they make great bathroom reading material.

The next step is reading code and knowing what that code is doing. Anybody can write their own code and know what is happening(for the most part). You need to be able to understand code written by other programmers. Just direct your browser to www.github.com and look for a project that sparks interest in you. Read through the code in the project, understand what the code is doing and write comments for the code. Not only will this help you get a better grasp on fundamentals but it will get you used to reading code written by others and get you used to writing comments. This is a practice that not only others will thank you for, but you will thank yourself when you go back to code you wrote 6 months ago.

As you start to grow into your own skin, you have to face harder challenges. Refactoring code is a great step in becoming the programmer you want to be. In order to do it, you have to understand the code your reading and use critical thinking to make it better. A great resource for refactoring code is (www.refactormycode.com). It allows you to take a stab at refactoring and see how others approached the task as well.

In closing I would like to mention some of the most obvious things to help you progress:

1. Learn your editor inside and out. Know all the shortcuts and things that make you faster with your editor of choice.

2. Test, test, test. Testing not only helps you understand what your code is doing it will make your life much easier down the road.(Also most employers require it.)

<p>3. Start your own project.  Don't start an easy project you already know you can knock out.  Start one that will push you beyond your limits and force you to learn new things.</p>
<p>4. Lastly, always be writing code.  Even if the code your writing is awful and makes most vomit at the sight of it, your making progress.</p>