While I don't claim to commit 10x more LOCs, I do write exceptional abstractions that allow me to get things done in a quick, robust way.
I've met far too many 'senior' developers blatantly breaking DRY because they don't really know/use all features $language or $framework has to offer.
My hunch is that as expertise increases for developers, LOC/day initially goes up, as they have to think less about language constructs and how to do certain things. Once a certain level of expertise is reached, LOC/day goes down, as the developer figures out how to do more with less code and spends more time in decision making and planning.
To be fair, those guys that throw out tons of code really explore the problem space. it's tough to start with a clean design when the spec is vague.
If you could achieve this feat, I'd say you are already a 10x type programmer. It's good you are better at abstraction, you may not be 10x but you may be 5x/4x and that's significant.
LOC is the worst measure of productivity, but sadly, most managers (mainly, the excel sheet type managers) find it easy because they can use LOC in their shitty formulas.