Well, my review came in today. Basically, it's a B. Not terrible, but not something to be happy about, either. Also not something to merit a bonus or a raise, neither of which I anticipated.
Most of my expectations and fears ended up being pretty accurate. The overwhelming majority of the text was directly related to my manager's interpretations of mails that he was CC'ed on, and you basically only CC someone's manager on something if you want to be a dick. So, that didn't come out well. The first half of the year is mostly irrelevant for the final review since there's a (mostly meaningless) midyear review that covers the first half. So, the half of the year where I was working on stuff that I had experience in and did a really excellent job didn't mean anything, and the half of the year where I was dropped into the middle of an ocean of legacy C++ code and told to "fix it" is what my review was based on, which is just cute.
What I failed to keep in mind is that reviews are based on how well you're doing as an employee who happens to be a developer, not how well you're doing just as a developer. Any miscommunication with someone else, even if it's cleared up, is a thing to be avoided. This sort of thing bit me several times. Also, things that I thought were friendly suggestions, like "make sure that other people on the team know the kinds of great work you've been doing" were actually assignments that I didn't complete. Had I sent out a couple emails to the team at random points telling them how awesome I am, I would have actually done better.
I was able to get my manager to take some parts out of my final review because they were simply things that he didn't understand. For example, he saw my first code review where my coding style was being nitpicked to death, and somehow drew the conclusion from that that I refused to follow the reviewer's coding standards because I thought they were stupid. In reality, I did think that they were stupid, of course, but that mail that he saw was the first I even heard of them, so I couldn't exactly be expected to have followed them.
And, of course, it did definitely hurt that at about 40-45 hours for a normal week and 55-60 hours for a crunch week, I work less than any other developer on the team.
So, I'm annoyed. Things are mostly as I expected them, but that doesn't mean I like it. I don't like these kinds of subjective reviews because I always seem to get screwed in them. I'm quiet and calm and humble, which always ends up being seen negatively, and when I do speak out, I'm blunt and honest, which ends up being seen as me being inconsiderate. Had I spent more time fixing inconsequential little silly bugs, ignoring the important ones, I would have looked better. Had I tooted my own horn as much as my manager wanted me to, I would have looked better. Those things aren't me. I guess in the future I have to decide how exactly to balance being me and being the person fairly similar to me who "plays the game" better and gets better review scores.