The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
My question is somewhat religious and definitely mundane compared to the guy who wants to write an OS in .net, but I live in the world of maintenance code. My bugaboo is consistency. Take a project of veteran developers (they each have their own style) add a few whiz kids (who have their own styles), add code standards that are pretty much ignored, and shake. The results can be mind-boggling. I've seen coding conventions deal with many issues, but I don't think I've seen one dealing with filenames and their construction. In the project I am re-factoring now, the file system is fixed. The primary folders in the root are fixed, so we have something like:
I have a lot of code that builds file specifications including folder names. A great deal of concatenation, removing slashes, adding slashes and what not, it just begs for errors. So instead of something like this:
Over the years I have learned not to care. I have seen and done both so when I start building paths I use PathAddBackslash because it adds one only if necessary. This way the code can accommodate both options.
Lately, I use no leading slashes and I have trailing slashes on directories. Plane, old file names never have them.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"