Describe what a class is

[PragTob]

Is missing as I believe it could get pretty complicated, maybe classes deserve their own section... but should definitely be in the cheat sheet.

Maybe a description along "the blue prints of an object" or something like this?

[abelards]

Wow, I agree with all of your other "content" issues but I don't know how to feel about this one.
The trolling answer is: "I'll do it if you can make two developers agree on what really is OOP".

This cheat sheet states clearly it doesn't mean to be perfect and accurate, but practical.
But explaining OOP is already complicated face-to-face in person, even more so in print.
Plus, "modeling" for Rails is neither OOP's class diagram nor DBA's tables schema.

It can be so easy to mess one's head with attempts to explain what classes are, I think they're best left out for now.

[jrgifford]

It can be so easy to mess one's head with attempts to explain what classes are, I think they're best left out for now.

Yeah, that's very true, and I agree.

[PragTob]

Thank you for raising those concerns!

I'd just like to have something about classes, since I think that's something that people might want to look up. But yes OOP is really hard... I was thinking of some small text along the lines of a "class as a blueprint to construct objects"