Boss: This is the latest documents we have.
Me: Oh, that's v2, I have v3 here, so I'll send them over to you.
Boss: But it has (3) behind the filename. Isn't that uptodate?
Me: Nah, that's a copy of a copy of a copy. That's why I put a v before the number! ;)
Boss: I don't understand...
Oh boy! 😋
#Work
@trinsec
that's why I always put the date in the filename
@StroomAfwaarts Yeah, sometimetimes I do that too. But as I can have multiple versions in one day... It depends on which documents.
🇳🇱
@trinsec what is you have multiple versions on the same date!
@freemo Pfft, v211213-1, v211213-2, etc :P
@trinsec so now you are back to using version numbers :)
@freemo Never said I'd never use version numbers!
@trinsec then why version with dates at all?
@freemo At least that way it's easier to see if Document A v3 is made around the same time as Document B v5. I can see the merit in that. Modified dates aren't always that reliable.
@trinsec fair, I'd just use the git timestamp :)
@freemo No git here. I'm doing it all manually.
@trinsec thats your problem then :)
@freemo Not really. The end results have to be different like this. If I'm the only one using git, it'd still be useless overall around here.
@freemo You don't know what a mess it was here before I arrived. People didn't know what versions of a document they were using. Some were smart enough to add dates to filenames, but still..
@trinsec fine fine, here ::hands you an AR-15::
@freemo That'd be a justified use of that stupid thing, actually. :P
@freemo (Especially against those who demand that 'I fix their document because I made it' but it turns out it's an unversioned document from before I joined and fixed it up...)
Versioning on filenames instead of using git....this is why we dont let Dutch people have guns, if they cant even version a file properly how can we expect them to handle a firearm!
I'll go for v<date> now. :P Today's version is v211213! Good luck making 211213 copies! :D