Especially if someone is looking for a raise. At least where I've work, the more senior engineers (i.e. the ones who have demonstrated that they should get higher pay) are the ones who are constantly evaluating new ideas and new architectures, reviewing other peoples code (in open-source, these people are committers, not just contributors), collaborating with other projects that integrate with ours, etc.
I get the point about everything being 100% new at a new job being more uncomfortable than the incremental newness you should constantly be experiencing. But still - if you do have a hard time justifying a raise, remember that you're asking the company to bet more money on your. Bet on yourself first, step outside your comfort zone a little, and try lead in a way you haven't much before.
But the fact is that it's just much much easier to convert ideas to code than code to ideas. It's also much easier to convert ideas to English than English to ideas, so better documentation probably helps, but it still sucks. (E.g. consider reading any sizable IEEE standard. It's all there, carefully described, but it's still a lot of work to understand.)
So yeah, many people prefer writing code to reading code, me including.
And BTW this is one thing that my university didn't quite get right. They focused a whole lot on writing code, but not as much on reading. The latter of course proved to be much much more important in my daily job.
That a person functioning as a software engineer expects:
a) Not to need to read or understand other persons code
b) Not to need to learn how new codebases work
Sounds completely unprofessional and misguided based on my experience.