I contend that developers can be bright, and have even genius aptitude for understanding and coding solo, without being GOOD developers. A good developer creates a quality piece of work, and makes the whole project better. Sorta like the really smart guy who hasn't enough common sense to brush his teeth regularly, and can't speak in public.
I'm not saying this is you, but one of the most frustrating programmers I ever worked with wrote more code than anyone on the team, and we had some good people. He plowed through swaths of stuff, leaving behind him ZERO documentation, impenetrable forests, and actually made some of my own code hard for me to understand (I can do that on my own, thank you very much!). Eventually he almost derailed the project, because he became a one man show. People could not follow him. We were not in synch as a team.
The thing I wanted from him was to slow down, and spend more time:
- Improving the quality of the codebase
- Communicating with the team
- Working on things that helped others as well as help him finish features / stories
- Fixing bugs
Question, does your code measurement count comments as lines of code? If so, there is an immediate way to maintain your line output while reducing your "bug ratio"; simply increase the level of comments you write (level = quality and quantity). Comments rarely have bugs (though they can be out of date) and in general, we don't have enough quality comments.