I did two projects on Rails that worked well, but in the process re-invented the wheel, working (and hot) water and painkillers, which, as I learned, were subsequently already present in the framework.
So basically, what is the best way to correctly recognize all the smart parts in a framework that will save time, and not build the functions themselves that have already been implemented? Reading documents from page 1 onwards? Is there a specific example application that reveals everything? A specific open source project? All the rails? Or something completely different?
A number of people offered a series of books, but I might not have made myself clear enough about what I was looking for. I already have several Rails books (and one Ruby) that explain the structure of Rails to varying degrees, but this is not quite what I am looking for. Example:
I encoded my own function to print numbers as currencies (I actually extended Object to do this for me) because I had no idea that number_to_currency existed. Now this is not very important from the point of view of time, but I am sure that I have done my own methods many times simply because I did not know that there is a similar rail function.
So, how can I find out that number_to_currency (and many other functions) exist?
source
share