I try to make everything Pascal case. It's easy to read in a terminal and pretty easy to type.
this post was submitted on 31 Aug 2024
210 points (97.3% liked)
Linux
55060 readers
883 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
FileName_IMPORTANTCATEGORIZATION.yyyy.ext
With all bits being optional (not every file needs the date it refers to)
So eg (slight modifications for anonymity):
SunLifeInsureance_SIGNED.2024.Q1.pdf
SpotDoesTrickAndFalls_ORIG.mp4
JSmithPassport_CANADA.2015_2025.pdf (I am a dual citizen)
JSmithCOVIDPass_DOSE1.2021.pdf
depends on the color of my mood ring
camel for java. flat for c
camelCase for non-source-code files. I find camelCase faster to "parse" for some reason (probably just because I've spent thousands of hours reading and writing camelCase code). For programming, I usually just use whatever each language's standard library uses, for consistency. I prefer camelCase though.
Gotta live the Ocaml_case
I took a CS class that was java based, and now my go-to is Pascal for file names. Sometimes I do flat or screaming just 'cause.
If its my own personal code, snake case, if I am sharing with my frontend devs then camel case. If I am writing short scripts, then flat.
Pascal or camel case for code, snake case for files and screaming snake case for globals
Related: a list and explanation of variable naming conventions https://www.pluralsight.com/blog/software-development/programming-naming-conventions-explained
Snake Case and Pascal Case is what I tend to default to
Kebab case with Pascal case in the usual places. I'd change to all kebab case but the muscle memory of typing Documents would nearly kill me.
my go_to NamingCovention: ANYTHING but camel-case 🤮
I use PascalCase for classes, camelCase for functions and variables, SCREAMINGCASE combined with snake_case for constants and for filenames/folders mostly snake_case with kebab-case if date or timestamp is involved.
generally i still to camelcase if i have no separators, if i do have separators i stick to - now. _ sucks. I use . notation when dealing with copies of files.bak or something like that.
If i feel really special i throw a space in the name just because
- Media:
Cool_file_name - Other:
cool-file-name
Pascal for server code running C# and Camel for client running TypeScript.
Pascal and Kebab case
2024-09-02_something-important_something-less-important
Since Linux is caps sensitive, at least I always use lowercase.
I guess I use kebab case for any file used for IT projects
load more comments
(1 replies)