I was warned before starting a rails project for the first time that it would be easier to make knowing the background Sinatra knowledge and having already created a Sinatra application, but not to take all of the built-in code for granted. Being that I have gone through building a Rails application I now know what they meant. I will say that even though there were a lot of similarities between the two and that rails has so many wonderful built-in functions, when build it out from start to finish you quickly see just how much more complex it is. One thing that shows that complexity is how rails has a completely different file for just that routes you’ll need, leaving the controllers as plain ruby classed that holds our actions and turns them into ruby methods instead of having it all displayed in the controller.
Some of the things built in rails that made the process of building my project just a little more awesome were the error messages available through validations in my models, and the rails generators you could type out in the terminal. The validations helped me with not only not having to put the errors in my code but also with my indecisiveness of what I want my error to say. When it comes to the generators, I used the resource option for the most part, it gave me a controller, model, created a migration table, and gave me the basic routes for each command I used.
For each project that I do I feel that much closer to my goal of being able to call myself a master-coder . I can’t wait to take my simple applications and turn them into something big and beautiful I can be really proud of
Top comments (0)