I'm going to probably put my foot in my mouth here and respond with MY BELIEF:
What DHH is talking about w/the CRUD concept is that if you really
break down your application and looks at its pieces, you'll see that
each component would fit the CRUD component.
- This is like Smalltalk saying everything is a message
- This is like any language that is Object-Oriented - look closely
enough and everything is an object!
- Java uses getters and setters for classes, which can be objects. And
with those objects, what do you do? You Create new ones, Update old
ones, Read and Delete them.
What DHH is saying about CRUD is nothing new, what I got from the
presentation is that he is pointing out how *well* this couples in the
web environment, with its different layers, and how this is a good
rule of thumb for working on your model:
Ex: I want to Read something about an object --> Use GET
I want to Update someting about an object --> Use POST
DHH gave you an example for your context, Registration. You'll want to
create new ones, delete existing etc.
When I'm stumped about trying to fit a 'concept' into programming, I
think of the verbs that entailed. What is the User doing? 'The user is
*authenticating* to my program.', 'The user is *registering* for an
Feel free to correct me anyone, my main point was that you shouldn't
think of this as the mantra for your life, just take note of how well
it couples with the other layers and follow it as a guideline.