Meeting 3: Database Design - ORM Arguments

Today we discussed the age-old question: "Should we use ORM, or should we not?"

Arguments For

Pro: ORM is like the cool kid in school. It's got all the right connections, and it's really good at hiding its mess.

More on ORM's pros

Arguments Against

Con: ORM is like the overachiever who just won't shut up about its own greatness. It's all like, "I'm so object-oriented, you know!"

And here's why we don't love it so much

But in all seriousness, what's really going on here is that our database is just not ready for ORM yet. We need to, uh, "mature" a bit more before we can handle all that objecty goodness.