- Present a solution along with the problem.
- Explain why the old way is bad and the new way is better.
- Keep it simple.
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||
|
This Month
Month Archive
Year Archive
Login
|
Thursday, August 31
by
BigJimmy
on Thu 31 Aug 2006 04:18 PM CDT
So after my last post about Mr. Clark's Rails no-nos list (now with extra followup!), I decided to act on Rob Sanheim's suggestion: that a site be created detailing the deprecated parts of Rails and solutions for same. I first thought of a blog, but I'm lazy and I don't want to write it all. Deciding that the Official Rails Wiki would be a much better (and easier) repository, I went there and found the perfect page already waiting for me: Deprecated Patterns. I filled it in, with the requisite bad wikiformatting (can't we all agree on what ' * ' means?). If you care enough to add an item, please play along with the best practices set forth below:
|
||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||