Thanks for the words of encouragement, I will definitely keep working away at it.
Ignore it. Programming is like any other skill, where mastering the fundamentals is the heart of it. There are a LOT of basic concepts---basic and composite data types and data structures, the difference between a thing and some kind of pointer to a thing, ways of repeating operations (looping or recursion), breaking big problems into small ones and building back up to the big, being aware of causes, symptoms, and cures for common errors (off-by-one bug, overflowing an int, testing floating point nums with equals, etc.)
What matters most is training these basic ideas into reflexes and learning to easily match combinations of these basics to most problems you encounter.
Learn the basics, then tackle lots of fairly simple, common programming tasks (google for sites that offer lots of programming exercises) until those basics become part of you. You should also work on "fun" projects of your own at the same time so it won't get boring. Forget the arcane and obscure features and techniques for a while. They won't make you a great programmer; mastery of the fundamentals will.
Django's ORM is a pretty good example of some great meta classery. The stack overflow question posted earlier is a good resource that you should bookmark so that you can look at it when you actually come across some meta classes.
I agree that it's an advanced concept, but it helps when people post stuff like that here and explain it so that I am at least familiar with it existing.
Rather than elaborating on that, there's a stack overflow answer that's often linked that is uncharacteristically decent at explaining here: http://stackoverflow.com/a/6581949/637787.
Note that as I said, I would suggest you completely ignore this and not even bother reading that right now.
This is very useful for introspection and dynamically building class structures. Which extends to it being also a common API for extensions to your classes (I'm playing with a Perl/Glib project using the Moose MOP framework to allow Perl classes to have Glib signals, for example). Speaking for Perl/Moose, it's regularly used to modify or extend the behavior/capabilities of attributes (by applying traits to them).
Even just the introspective aspect means your program can easily know about the structure of your classes, for serializations, debugging, proxying, auto-generating documentation, auto-generating command line arguments, and so on.
This is just a rough outline, and in no way complete. I'd guess here's a good language-agnostic starting point: http://en.wikipedia.org/wiki/Metaobject