Skip to content

Instantly share code, notes, and snippets.

@kabir4691
Created August 12, 2020 12:47
Show Gist options
  • Select an option

  • Save kabir4691/8d25128435a0d69d2e50875fdc54559e to your computer and use it in GitHub Desktop.

Select an option

Save kabir4691/8d25128435a0d69d2e50875fdc54559e to your computer and use it in GitHub Desktop.
Finished watching the Ruby on Rails 5 course from PragmaticStudio (directly online). Went through their accompanying exercises too. The series did a great job on explaining the basics of Rails by developing a simple events web application. What I appreciated was them going through all the conventions that Rails assumes, which results in boilerplate code being generated upon using a certain syntax. The convention based approach has me in two minds, to be frank. Firstly, I am glad that Rails takes care of ensuring an uniform code base and structure throughout an app, which would vastly reduce any friction while working with team members of varying experience levels. Secondly, the 'cannot opt out' nature of the conventions on the other hand makes me wonder at the difficulties in building applications with custom settings or design patterns. The assumptions Rails makes forces one to go through the entire code before doing a rails generate command. However, I think with the passage of time, that should start feeling normal, hopefully.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment