Close

A Sharpened Directory Environment

nicholas-jacksonNicholas Jackson wrote 10/09/2022 at 21:46 • 1 min read • Like

After discovering that most Linux File Systems and NTFS both support almost any character in a directory name, I've started playing with how I want to setup my developer environments.

I want a system that is easy to access, reproduceable on any system I would use, and follows a standard file hierarchy. I also want the name not to be locked down to just source code (like dev, build, src, etc, repo), but project-oriented files in general (like image-editing, project management files, etc)

To make access easy, any developer/project root directory will be named "#". My reasoning for choosing this symbol is simply: 

In directories with duplicates (or on platforms that don't support this symbol), you can choose from any number of names to replace it (projects, hash, hashtag, tag, #tag, #project, sharp, pound, etc)

I may change this in the future. Hopefully, it doesn't break anything. Ha Ha

As for the structure within the directory, I try to replicate the linux/unix standard for naming directories as closely as possible. The original standard used on Linux can be found at:

https://www.pathname.com/fhs/

Like

Discussions

Nicholas Jackson wrote 10/10/2022 at 20:19 point

I've also started to discover the benefits, of separating my developer projects from the rest of the file system. First benefit, is for hacking. If I get into practice of installing necessary binaries manually, I can bypass several windows security features that prevent software installation

  Are you sure? yes | no