Why The Reverse Engineering Part Of Learning Ruby On Rails Makes Sense
So I’m learning RoR (Ruby on Rails), and I’ve been amazed at a specific way of learning it (the way that http://guides.rubyonrails.org) teaches you.
I’ve worked with CodeAcademy, which is a website that takes you through tutorials on most modern programming languages, I’ve watched a guy code in Python, on a video tutorial, and coded along with him, and now learning to use rails, and getting to know the language of Ruby, I’m taking this reverse engineering approach (based on the guide above, at guides.rubyonrails.org
I appreciate good, well thought out instruction. I study neuroscience, am fascinated with learning, and really get excited when I find a tutorial that really aligns well with how my brain works.
And this is one of them. Simply, the reverse engineering part, which a friend of mine and UI engineer for Work Day suggested, is working really well.
It allows you to write code, that a guide document tells you to write, and then see (in your actual web application, in the browser) what it does. Then you can reverse engineer how it all worked.
Now I understand what this means:
I coded it, looked at what it created, (a simple comment form) and then tried to understand what all of the details meant. That solidified the syntax, and the code itself, so much more than any other tutorial on the web. But it’s still early.
Just wanted to express my excitement about it – When you learned RoR, if you did, what was the best way for you to learn? And did having prior programming experience effect that? (I have about.. Zero)