I think the quality of the code depends a whole lot more than the speed at which it is written. Badly written code wastes everyone else's time, and can often be ridiculously difficult to maintain (or debug). The other "time sink" is bad design choices with the result that most (or even all) of the code needs to be rewritten. When working in a team, what's important is "everyone's time", not just the time of one coder.
On the flip side, if a person can code fast because their code has very few bugs (or bugs are caught early), or because they look things up on Google / Stack Overflow a lot less frequently than the average coder, or because they follow best practices + a very efficient workflow, then I think the credit is deserved. And even more so if the person is able to translate those skills to help everyone else on the team to become better coders (it's a team effort after all).