My new pet peeve - final
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
At the risk of starting a war, why not just check the last modified file property? Free versioning that comes with every platform.
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
Final is a myth! Dracula proved this with the Lochness monster's resources when Bigfoot's cousin came to oversee the project after Santa Clause's wife gave him the spring off to visit the Sandman on his holiday to the tooth fairies' palace on the other side of wonderland, knowing the boogey man will try and intervene in proving Final as the truth just before the Easter bunny can use a Leprechaun's wand. :suss:
Chris Maunder wrote:
This is why documents need source control...
I give you version control document.docx documentV1.docx documentV2 - DG-comments.docx documentV3.docx :-\ then at least one knows of the laziness if "Copy of Copy of documentV7.docx" is found :doh:
Loading signature... . . . Please Wait . . .
-
If more than one person will be working on the document simultaneously then source control (like SVN) is the best option. For documents you are working on that others are not contributing to try the following naming convention. It works for me. document20140103.docx document20140131.docx document20140206.docx document20140223.docx document20140316.docx You will always know the latest and greatest version of the document. Well at least the latest version. :cool:
**_Once you lose your pride the rest is easy.
I would agree with you but then we both would be wrong._**
The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopesAnd if it becomes even more intense one can add the HHmmss :rolleyes: document20140103_085219.docx document20140103_090659.docx document20140103_102534.docx document20140103_102601.docx document20140103_103754.docx document20140103_115910.docx document20140103_142101.docx
Loading signature... . . . Please Wait . . .
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
... and this, dear reader, is what document control is for.
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
Chris Maunder wrote:
This is why documents need source control
Been there, done that, got the revision history to prove it. My sub-peeve to your pet-peeve: People who include the revision number in the document filename. I have one document in source control "
MSEM_Interface_121.docx", "MSEM_Interface_122.docx", ..., "MSEM_Interface_137.docx" :doh:.Software Zen:
delete this; -
No version control problems - give them a Wiki. Let them fight it out amongst themselves.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"As far as we know, our computer has never had an undetected error." - Weisert
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
Do you really want to let a marketing schmuck edit a wiki?
Software Zen:
delete this; -
My solution to this common problem is to rename older versions of the document, e.g:
Document.docxThe latest version of the document.Document - 01.docxFirst edit.Document - 02 - Updates per JoeUpdates made in response to Joe's review.Document - DraftAn unsequenced draft version of the document.
Chris Maunder wrote:
This is why documents need source control...
Of course they do! As does any edited collateral. Aside: File versioning came standard with my first OS (VAX/VMS, circa 1980). :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Ravi Bhavnani wrote:
Aside: File versioning came standard with my first OS (VAX/VMS, circa 1980)
PURGE *.* /KEEP=3
Software Zen:
delete this; -
You'd think. Except it isn't. You've had merge conflicts before, right? Same deal.
cheers Chris Maunder
So use a version number before Final in the name to imply it's baselined. Then increment the version number before finalizing and always remove Final while it's a work in progress. document_1.0.doc document_1.1.doc document_2.0_Final.doc document_2.1.doc document_2.2.doc document_2.3.doc document_3.0_Final.doc
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
-
Ravi Bhavnani wrote:
Aside: File versioning came standard with my first OS (VAX/VMS, circa 1980)
PURGE *.* /KEEP=3
Software Zen:
delete this;Username: GWHEELER
Password:Welcome to VAX/VMS 3.1.Your last login was Mon 14-Jul-2014 07:24:08 AM.
/ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Username: GWHEELER
Password:Welcome to VAX/VMS 3.1.Your last login was Mon 14-Jul-2014 07:24:08 AM.
/ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Your attempt to put me into a state of maudlin sentimentality has succeeded, Ravi. Well played :-D. My last experience with a VAX was on a MicroVAX-II back in the late 80's. I worked for a defense contractor at the time. We developed simulations in FORTRAN and Ada. I also used the machine when I was taking graduate artificial intelligence classes. I *cough* borrowed *cough* a friend's C compiler and ported XLISP[^] from the IBM PC to the VAX.
Software Zen:
delete this; -
Your attempt to put me into a state of maudlin sentimentality has succeeded, Ravi. Well played :-D. My last experience with a VAX was on a MicroVAX-II back in the late 80's. I worked for a defense contractor at the time. We developed simulations in FORTRAN and Ada. I also used the machine when I was taking graduate artificial intelligence classes. I *cough* borrowed *cough* a friend's C compiler and ported XLISP[^] from the IBM PC to the VAX.
Software Zen:
delete this;Looks like we've walked similar paths. :) I met my first VAX in 1980 at school, and later in 1987 when I joined DEC's AI group. There we used a bit of VAX Lisp, but mostly DEC OPS5 to build XCON[^]. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Looks like we've walked similar paths. :) I met my first VAX in 1980 at school, and later in 1987 when I joined DEC's AI group. There we used a bit of VAX Lisp, but mostly DEC OPS5 to build XCON[^]. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Ravi Bhavnani wrote:
There we used a bit of VAX Lisp, but mostly DEC OPS5 to build XCON
We talked about XCON in my AI classes. The opinion was that is was one of the first (if not the first) genuinely useful commercial AI applications. I seem to remember the professor saying there was a sign at DEC that said "Last year I couldn't even spell 'knowledge engineer', and now I R1." :cool:
Software Zen:
delete this; -
Ravi Bhavnani wrote:
There we used a bit of VAX Lisp, but mostly DEC OPS5 to build XCON
We talked about XCON in my AI classes. The opinion was that is was one of the first (if not the first) genuinely useful commercial AI applications. I seem to remember the professor saying there was a sign at DEC that said "Last year I couldn't even spell 'knowledge engineer', and now I R1." :cool:
Software Zen:
delete this;Ha ha ha! That was a quote from my boss, John (McDermott): "Three years ago I wanted to be a knowledge engineer, and today I are one." Throwback Tuesday[^] :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Ha ha ha! That was a quote from my boss, John (McDermott): "Three years ago I wanted to be a knowledge engineer, and today I are one." Throwback Tuesday[^] :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Awesome. Think the youngsters are annoyed at the old farts and their war stories yet?
Software Zen:
delete this; -
Awesome. Think the youngsters are annoyed at the old farts and their war stories yet?
Software Zen:
delete this;You're right.
^Z. :) /raviMy new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
-
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version. In itself this isn't awful. What's awful is: document.docx document - final.docx document - final - DG-comments.docx document - FINAL.docx So which one's the final one? This is why documents need source control... [Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers Chris Maunder
Which one is the final document? It must be the one named: document - REALLY FINAL - and we mean it this time.doc
-
We have live servers with new at the front of the name. I hate to think what we'll have if they need replacing again.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
Simple: Newer. Next update: Newest Final update: Newester
