TechEcho

I try to have some structure in my filenames and use the convention of <base filename> V<version #> <initials> <change description>.ext. This doesn't help the problem of differentiating drafts and final versions so I still end up with things like Year End Report Final V3 BCG minor edits.docx. How do you name your documents and/or folder structures to handle this?

just put a date (in YYYY-mm-dd format, so it sorts properly) somewhere.<pre><code> report 2022-09-01 draft.doc report 2022-09-02 draft2.doc report 2022-09-03 final.doc report 2022-09-04 draft4.doc </code></pre> (A more powerful way is to use some sort of version control system; but those don't generally work well with non-text documents.)

I TYPE FILENAMES IN ALL-CAPS SO I CAN READ THEM BETTER.I tag filenames using square brackets and use hyphens. For example:HOLIDAY [JUNE-2022-BEACH].jpg

I name them<pre><code> git init .</code></pre>

I TYPE FILENAMES IN ALL-CAPS SO I CAN READ THEM BETTER.I tag filenames using square brackets and use hyphens. For example:HOLIDAY [JUNE-2022-BEACH].jpg

I name them<pre><code> git init .</code></pre>

Ask HN: How do you name your documents?

3 comments

Ask HN: How do you name your documents?

3 comments