Rethink mass assignment outright. Ask hard questions about whether attr_accessible belongs in the model, in the controller, in some kind of view entity, or whether there really ought to be a form do-hickey that helps a view render and also helps a controller process the result. There’s a lot of interest in DCI (Data, Context, Interaction). Is attr_accessible a role responsibility?
Come to think of it, why are models so damn fat? What’s a form doing only assigning some of a model’s attributes? Should it really be posting to a smaller model that is composed into a bigger model?
This is the second-to-last post on this blog.
I haven’t updated this since early February, and while no one has asked about why, I figured I’d say something:
1) I’ve met the woman who I have a good chance of spending the next few years or longer with in November. We’ve been ratcheting things up several notches since.
3) All I’ve really ever said here, besides music best-of lists has been quotes. I don’t feel the need to share these any more.
4) I’m eventually going to do up a blog on a different platform, whose uptime I have a bit more control over. Probably static files on github pages or S3; perhaps wordpress on phpfog if I can find a way to tolerate wordpress. I’ll be writing about things with a bit more depth than I ever have here. When I get that going, the link to that will be my last post here.
It’s been fun, tumblr, but I’m a different person now. Thanks for the memories.
STOP. DO NOT PASS GO. DO NOT COLLECT TWO HUNDRED DOLLARS.
Natural Ice, in case you were wondering.
Remember kids, when Google says “open” they mean “Google”.