There is something about understanding the process of a methodology that is more satisfying than understanding that it works.
The most universal example of this that I can think of is a car. It is one thing to understand that a car runs on gas versus understanding how a car engine functions and how it manipulates the various parts of a car to propel it forward.
When we first started learning Rails, it seemed like magic. This is largely because we learned how to program command-line applications that forced us to write out every process of the methodology and user interface of the application. Geek-syntax FTW!
Turns out that when you start a rails app, a large part of the application-design process is relegated to the back-burner. It's already created in your Rails app!
So why is this a good thing?
If you've studied the processes that make up Rails, you not only appreciate it more but you can actually manipulate it. You can create methods, classes, and controllers that are specific to your app. This is important because who wants to build a cookie-cutter application?
Most importantly, it shows you what is going on beneath the magic of Rails and ActiveRecord. You understand what is really happening under the hood. You get an appreciation of the technology and its potential that would not be realized unless you learned it the hard way -- i.e. without "the magic."
So don't skip ahead. Learn what's going on under the hood of Ruby, Rails, and other languages that make up the web development process. Don't skimp on your html, css, and javascript. They will come in handy when putting your app together.
The most universal example of this that I can think of is a car. It is one thing to understand that a car runs on gas versus understanding how a car engine functions and how it manipulates the various parts of a car to propel it forward.
When we first started learning Rails, it seemed like magic. This is largely because we learned how to program command-line applications that forced us to write out every process of the methodology and user interface of the application. Geek-syntax FTW!
Turns out that when you start a rails app, a large part of the application-design process is relegated to the back-burner. It's already created in your Rails app!
So why is this a good thing?
If you've studied the processes that make up Rails, you not only appreciate it more but you can actually manipulate it. You can create methods, classes, and controllers that are specific to your app. This is important because who wants to build a cookie-cutter application?
Most importantly, it shows you what is going on beneath the magic of Rails and ActiveRecord. You understand what is really happening under the hood. You get an appreciation of the technology and its potential that would not be realized unless you learned it the hard way -- i.e. without "the magic."
So don't skip ahead. Learn what's going on under the hood of Ruby, Rails, and other languages that make up the web development process. Don't skimp on your html, css, and javascript. They will come in handy when putting your app together.
