5 ms·
From reddit: “This is basically the report_final_FINAL2.docx of register names.”
by jpxw 7y ago
From reddit:
“This is basically the report_final_FINAL2.docx of register names.”
- read_if_gay_ 7y agox86 in its entirety is report_final_FINAL2.docx
- nitrogen 7y agoWhere does that filename meme come from?
- pas 7y agoPeople's "Downloads" folder being full of New folder", "New folder (1)", all of them being full of similarly named documents. Also anyone not using proper version control (business folks, designers, scientists, students) usually has a bunch of files all over the place with every kind of inconsistent names for a bunch of versions.
- psychoslave 7y agoI can use proper version control for code, but when it comes to office products, I use an ISO date to prefix my "versions" of files. This is really an integration of proper version control within the workflow. I don't find it appropriate to blame the user when they are so misguided. Don't get me wrong, an ISO date prefix is nothing close to perfect for version control, but it: - works anywhere you are asked to name a sequence of things - tacitly communicates well the naming scheme so your colleagues can get it and possibly even start to imitate it - give a clear time referral - isn't sensible to system time-stamp, so this keep the chronology even when file are touched or copied elsewhere with a different time-stamp - spontaneously generate a chronologically ordered result of versions when their are displayed in list Once again, this is not my favorite way to organize things. But from a practical point of view, it often comes as the less worst solution you can run seamlessly.
- Hendrikto 7y agoWhat hurts most is the ".docx" part
- pizlonator 7y agoThat analogy only works if “report”, “report_final”, and “report_final_FINAL” were all released, were insanely successful and made you a billionaire and then you didn’t want to lose the customers that liked those versions when you made some small edits.
- skocznymroczny 7y ago_new2