The subject is broad enough to be of interest to all web developers, not just Ruby developers. I hope to see you there!

Zurich: www.meetup.com/rubyonrails-...

Geneva: www.meetup.com/geneva-rb/ev...

I love namespace, it's great to group related things.

As always it's a tradeoff, but when I'm unsure between add column or create table, I always go for the new model.

Migrating a column is painful and particularly if you can't afford interruption since the application must handle both cases at the same time.

I don't remember to have regretted to create an extra model, however I already regretted many times adding an extra column instead of a table.

Thus, there is an interesting indicator: number of columns / number of tables. I'm sure that code bases with a lower ratio are healthier.

It's a lot better because it enables to store more data (IP address, timestamps, ...), and gives a lot of statistics such as how many reset password attempts during the last hour for a particular user?

The wrong way is to store confirmation_token, reset_password_token and session_token in the users table. In fact, that should be 3 distinct models: User::Confirmation, User::ResetPassword and User::Session.

Mine is starting to peel too.

Always take both 😀

And Switzerland is in Schengen but not in EU 🙃

That’s another problem 😅

No internet and no phones is also a good was to increase productivity 🙂

One new subscriber.

And a nice CSS to print the page as PDF, if the invoice is not sent by email.

Incredibile 🙂