10 things you should know before learning ruby or rails
•Download as PPTX, PDF•
0 likes•299 views
Learning Web Development. Learning Ruby. Learning Rails. Learning Ruby or Rails. Learning Ruby on Rails. Learning to code.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (18)
Similar to 10 things you should know before learning ruby or rails
Similar to 10 things you should know before learning ruby or rails (20)
Recently uploaded
Recently uploaded (20)
10 things you should know before learning ruby or rails
- 1. 10 Things you should know before learning Ruby or Rails
- 2. NO! Don’t Learn Rails before Ruby
- 3. If you take the time to fully understand Ruby before you learn Rails; then learning Rails will become a piece of cake. Whether you build controllers, actions or else, it will all come down to Ruby.
- 4. Understanding Ruby will also allow you to be more agile with rails and being able to go directly to the source to understand any methods or class.
- 6. Blogs can confuse you Unless you are reading a blog post such as “How to learn rails”. As a newbie, blogs that teach you rails won’t help but confuse you. There is one simple reason for that: Ruby and Rails have different practices depending the versions. For instance; the asset pipeline was introduced in Rails 3 and a lot of blogs won’t tell you that but assume that you already know.
- 7. Ruby and Rails Versions Ruby is a growing language and there are hardworking people that are still improving it. Same thing with Rails. As the language and framework improve; a few things will change. For someone that have absolutely no experience with ruby/rails noticing a change is like looking for a needle on the grass. A good thing to avoid confusion between ruby or rails version is to first figure out what’s the difference between them.
- 8. Asking Question About Everything to Everyone Everything you need to learn are in books. Figure things out on your own! You’ll become a better problem solver. Don’t expect people to build the code for you, figure it out on your own. ABG! Always Be “Googling!”
- 10. Reading Books* over Blogs. Learning Programming by Chris Pine Learning Ruby the Hard Way by Zed A. Shaw The Rails Way by Obie Fernandez The Ruby on Rails 3 Tutorial by Michael Hartl
- 11. Interactive Courses Rubymonk Codeschool Coderwall Railscasts
- 12. Not Copying/Pasting Code Even today I still type code line per line. It helps you to remember codes and it’s a good practice to have when learning a new language. Typing every single line of code you read has a tremendous effect on your memory. Just do it, You will remember
- 13. Not getting tired of Google-ing The web is vast enough and the chances are that you will find something out there that could solve your issue. There will always be things that you can’t remember or that you would like to verify or double check. Read ‘Why googling is the most important skill a developer *must* have.’
- 14. The faster you’ll be able to find something on Google or Stackoverflow, the faster you will be able to resolve issues you’ve never seen before that other people have already experienced.
- 15. Reading Documentation and Source Codes If you are stuck and nothing online can resolve your issue: Go back to reading, because the chances are that there must be something that you didn’t quite understand.
- 16. The Ruby on Rails Guide* Most people skim it and to be honest, the first time I read it I actually skimmed it too. entire form.Always come back to the Rails guide and never assume that
- 17. I Learned Ruby on Rails in 2 months…
- 18. ok!..18 hours a day…but I found a better way…
- 19. …so I wrote a book about it to share it
- 20. so… if YOU believe that people CAN or NEED to learn how to code faster
- 21. CONTRIBUTE TO THIS BOOK AT http://igg.me/at/learn-rails Click Here and DONATE THIS IS THE CROWD-FUNDING CAMPAIGN I STARTED to support the book
- 22. YMMD! Thank you!