On 15 March 2012 12:43, Mohamad El-Husseini <[email protected]> wrote: > @Peter, good point, although I don't think it's so bad to write your own > basic authentication then add something like OmniAuth if you require other > authentication methods.
Writing your own is a good thing to do, you get to learn about the sort of issues that have to be tackled and it is a real world problem that will be more satisfying than solving "towers of hanoi" and the like. The problem is recognising when to stop, each additional feature will probably be quite small and not look like a lot of work but over time they all pile up and the rest of the site starts to become entangled with the code which make replacing it very hard. It's something I've seen quite a lot so I try to avoid reinventing any wheel if I can help it. The pain I have had at work because of some code that has too much ego invested in it is virtually endless. I try to write the least code possible to do a job so that I can throw it away easily. Besides unless you are specifically writing an authentication and authorisation system then the time you spend on it is time not spent developing something that does not exist as a gem. For the record I have written my own tagging system because the gems that were available when I developed my site four years ago did not have the features that I wanted. So there are times when you have to. Peter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
