If you're gonna try the macro, watch out for typos, I didn't test it or anything prior to posting. I was actually kinda hoping one of the whiz kids would offer something really slick.
Actually, I'm the one that names them like that
where's my patented kneecap ventilator
In my mind, why try to decifer a code of characters when I don't have to anymore?
Descriptive naming is important (see the word VENT in my sample), however, as you can see by the length of this simple macro code, that the volume of characters has made the coding much less friendly. In coding, I've leaned that the more times I hit a key the more chances I have of screwing it up.
I mainly have this view from when I look for a block that is in our blocks folder (created well before I came to work here). Takes so much time to do this. Was really bad when it was "RES1007.dwg" , "RES1008.dwg" , "COM1248.dwg" , etc.
musta' been an architect. I'm all for descriptive names, but you don't need to completely spell out ELEVATION or CONTINUOUS.
Using my sample of "VENT-CR-E-F",I prefix the name with what the name of the element, in this case VENT. I know I'm looking for a vent, so this will help in sorting, it will also help if I later begin to extract data from the drawing, followed by a description CR=Cont.Ridge SOF=SOFFIT, TRB=Roof Turbin etc., followed by the kind of view E=Elev P=Plan and direction for elevations F=Front S=Side. Nearly everything we do follows this or simliar conventions.