Quick Tip: File naming convention
File Naming Convention
In my experience collaborating with others on a common document is challenging unless there is a single scribe. One problem that often reoccurs is file versioning. That is multiple people editing a file and saving their own copy.
Options for file versioning
There are solutions in place to fix this problem. Microsoft sharepoint comes to mind. It also sends chills down my spine to think about checking documents in and out. Sharepoint hasimproved over the years but I still find it sub par for most tasks. It may work well for arching documents that aren't modified often.
Current Repository Solution
The solution I use for storage is a box.com account. This provides retention of deleted files and the ability to easily share files with my peers. Once others have access I find it is usually helpful to explain my naming convention.
How I name my files
I use a specific format. It begins with YYYY-MM-DD followed by customer name, a dash, the project name, and usually end with a revision. For example if I recently worked on a wide area network (WAN) design for Acme Co. The filename would be similar to:
20151013 - ACME Co - WAN Design r0
If you check out the links below they suggest using a descriptive name and not using spaces. I like that advice but prefer the readability of spaces over underscores. If I were starting over I might train myself to use underscores.
Do you use something similar? Please share your naming convention. I'd like to know what is working for others.