I don't think you're committing career suicide. I've seen people get serviceable results out of it, and it always involves reading the code in depth. Reading the code being slower than writing it, they're almost never getting a speed up.
That being said, the better coders I've seen aren't looking for a speed up, they're generally looking for something to bounce ideas off of, or to get a first draft going to defeat writer's block or something (I guess this is technically a speed up, but not the way people mean when they describe slinging tokens around). It's generally to wind up at a better solution at the end than to get a sustained speed up (which seems to only be possible in boilerplate heavy domains, but those were previously slowed down by the boilerplate and are really only coming up to speed with everything else, at significant cost).
That being said, the better coders I've seen aren't looking for a speed up, they're generally looking for something to bounce ideas off of, or to get a first draft going to defeat writer's block or something (I guess this is technically a speed up, but not the way people mean when they describe slinging tokens around). It's generally to wind up at a better solution at the end than to get a sustained speed up (which seems to only be possible in boilerplate heavy domains, but those were previously slowed down by the boilerplate and are really only coming up to speed with everything else, at significant cost).