I’m not a programmer (yet) and I’m not a blogger (yet). So basically, I have no idea what I’m doing. All I have is a goal, and that goal is to learn Ruby on Rails.
The goal spawned from a vision for a web application, but instead of hiring a programmer (you know, the guys who actually know what they’re doing) I’ve stubbornly decided to build the app myself. I have settled on Ruby on Rails as the best language and framework for the job, but after several failed attempts to learn Rails, I realized I have been going about things the wrong way. If you’re a non-programmer and have ever tried learning Rails then you may have run into the same problems I have:
1) RAILS IS MAGIC. And that’s not a good thing. According to nearly every tutorial I’ve read on Rails, all you have to do is type “make my friggen application” and BAM! Your application is done, just like that! Well, there might be slightly more to it, but that’s the gist of every tutorial I’ve read… and that is just not how I learn anything. I need explanations of what is going on and why everything is happening, and I just haven’t been able to find these things.
2) “Rails reads like English”. BULL! As far as I know, the English language doesn’t use brackets, question marks, or periods in the middle of a sentence.
Though there are several more, those are my two biggest gripes about Rails. After my failed attempts at learning Rails, I’ve come to the conclusion that learning Ruby then Rails is the way to go. This blog will act as an archive of what I’ve learned along my journey, and will hopefully help others learn as well.
Would you like to join me? Let’s Ruby.
- a guy named loren
