DISQUS

Thanks for mentioning Poolr! I was the lone Rails developer on our team, although we had an amazing graphic artist, as well as a member who did some great research and even pitched in on the CSS. I like your ideas for the site, and we'd certainly like to help manage carpools, not just play matchmaker :)

We'll be launching the fuller, production version early next year. Still looking for the best city to launch with! We're also looking to develop an office version in parallel that will be open-source, for companies to support the carpooling efforts of their employees.

I was having trouble wrapping my head around the "why" to the Law of Demeter at first. I'll post my thoughts here in case they help someone else.

Bottom line: as soon as you refer to self.customer.wallet, you have forced the paperboy to know and abide by the inner workings of the customer. What if you want to change that someday? Maybe our customer wants to write a check. Heck, maybe he wants to check his wallet first, and write a check if he doesn't have the payment in cash!

Coding customer.pay(amount) means never caring how the customer will choose to pay in the future. You access the customer interface (the pay method) and go about your happy life. This code is tons more maintainable, because changing how a customer pays doesn't affect any other models that require payment.

The timestamp columns created are actually 'created_at' and 'updated_at', both datetime fields. The suffix '_on' denotes a date field, and the suffix '_at' denotes a datetime field. Thanks for the blog!