Isn't this a bit immaterial to the post at hand anyway?
1) your reputation in the community. I for one have never heard of you, so that leaves
2) code quality of the examples that you posted. a reader could infer that this may be good advice based on the fact that you appear to generate good code.
In this case your code is clearly not very well thought out, so why would the reader put trust in your unsubstantiated opinions?
In case you weren't aware, samples that don't require a ton of context are a particularly hard problem for informational posts like this. If you have feedback on the ideas I presented I'd be glad to hear them but I still fail to see how nit-picking an obviously early in-progress application proves anything.
I, too, keep finding myself in utterly painful Rails code. Now, if I may use your metaphor: Most of it is due to the blind leading the blind, per se. Programming novices discover some new rails thing, ruby thing ("method_missing" is the worst offender), or even a new programming pattern such as Command, and think it's the most incredible thing they've ever experienced, so they write a blog post about it. Other programming novices read the blog post and then go off on a rampage, overusing that concept and writing all the shitty rails code that I am currently maintaining.
There you have the ruby community in a nutshell.
Infact, the whole persistence mechanism is rather mystifying - an in memory store? What if I accidentally the power?