in reply to Code Maintainability
Even though I currently only write markup languages (starting to learn Perl lawlz), most of this makes good sense to me. I'm not a big fan of stuffing everything on one line just to do it, but if I can use shorthands for values I do. It's true, if someone can't read shorthands (esp if they are in the specs) then they shouldn't be reading it at all.
The "wider vocaulary" part works too. It's part of "use the right tool for the job" as usually this means less hammering around to get the ill-fitting piece to do the job someone else should've been doing, and if you don't know what's possible, you'll find yourself using a screwdriver to hammer in nails more often.
You know code is too bloated when you can clean it up, make it half the size it was and get exactly the same result with just as much readability as anything you would've written yourself.