realsilly writes: "I am a requirements analyst, and I often find myself in companies where they either have an extremely rigid naming convention and structure for storing documents or there is no structure in place at all. I find myself in the latter of the two situations, where I'm trying to come up with an easy to use and implement naming convention that will be followed by those who don't name things formally. I am avoiding using numbers and dates within document names and in many cases, I have much of my early documentation on internal wiki pages. I'm looking for some best practices ideas from the Slashdot community."
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's now on IFTTT. Check it out! Check out the new SourceForge HTML5 Internet speed test! ×