Depends on what the word is.  There are very commonly known abbreviations that it would be silly to spell out, like saying Coordinates for Coords, or Rectangle for Rect, or GraphicalUserInterface for GUI.  I've used fName so many times in so many different environments that to me it looks just as common as Coords or GUI and I don't even think twice about it.

As for "protected", I have a strong distaste for telling other people they are disallowed from deriving a subclass of my class, and if you throw around the word "private" everywhere that's sort of what you're doing - locking down so much of the behavior that there's not much left for a subclass to alter.  I tend to only resort to private if I think subclasses need to be utterly disallowed from changing it, because that's what it means.  I think making a thing private should be a decision that takes just as much thought as choosing to make a thing public.