4 ms·
I tend to ask, not how you use the framework, but rather how the framework works. How does routing actually work? How do named scopes work? How would you imp
by tyler 17y ago
I tend to ask, not how you use the framework, but rather how the framework works. How does routing actually work? How do named scopes work? How would you implement the {before|after} filters on models... etc.
It's actually somewhat more difficult to tell whether someone knows how to use Rails well. My only suggestion is to sit down in front of an editor with them and work through actually building something small but meaningful.
- judofyr 17y agoIf someone asks me how Rails works, I wouldn't be able to answer. It's just something I don't care about. Sure, give me a few hours and I'll figure out everything you asked for, but right off the bat? No way.
- tyler 17y agoIn my opinion, that's a problem. If you don't understand what is actually going on under the hood, you're likely to get bitten when things don't go exactly as you expect. ActiveRecord is the most obvious example of this. If you don't know what queries it's going to throw out for a particular call, it may work just fine in development but could easily bring down a site in seconds in production. Routing is another example. If you have a particular action that needs to have as low latency as possible changing its position in the routing file is often one of the easiest and most effectual changes you can make. Someone who just codes in the framework and doesn't understand how it works is unlikely to realize that.
- Zarathu 17y ago>How would you implement the {before|after} filters on models... etc. Models, or controllers? :)
- tyler 17y agoOuch. "filters" wasn't the right word there. Sorry about that.