There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

Whats your go-to naming conventions?

As far as I know there are these;

  • Camel case = coolFileName
  • Snake case = cool_file_name
  • Kebab case = cool-file-name
  • Pascal case = CoolFileName
  • Dot notation = cool.file.name
  • Flat case = coolfilename
  • Screaming case = COOLFILENAME

Personally I prefer the kebab/dot conventions simply because they allow for easy “navigation” with (ctrl+arrow keys) between each part. What are your preferences when it comes to this? Did I miss any schemes?

saigot ,

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

Lettuceeatlettuce ,
@Lettuceeatlettuce@lemmy.ml avatar

I try to make everything Pascal case. It’s easy to read in a terminal and pretty easy to type.

2xsaiko ,
@2xsaiko@discuss.tchncs.de avatar

For files? I like title case (like in article headlines). For example, I have a “Shell Tricks.txt”. I’m not really consistent though, sometimes it’s all lowercase or whatever really.

fuzzy_feeling ,

spaces in filenames?
oh, my sweet summer child.

2xsaiko ,
@2xsaiko@discuss.tchncs.de avatar

I don’t use a computer from the 90s. It can handle it.

MimicJar ,

I use flat case most of the time, but I also try to stick to single word files so there is no case to get in the way.

I think for documents I might share like a PDF I’d use Pascal case.

In a classroom or teaching setting I will sometimes use Kebab case as I find it is the least confusing and makes it extra clear where the word division is. Similarly I avoid Dot notation since it’s confusing for folks coming from a Windows world.

And I would avoid Screaming because that’s just too loud anywhere.

joeldebruijn , (edited )

Isnt CAPSLOCK case for screaming? 😁

GustavoM ,
@GustavoM@lemmy.world avatar

YEAH CRUISE CONTROL BABY

possiblylinux127 ,

My file

jjjalljs ,

Snake case, usually. Some perhaps unfounded fear that something will blow up on a dash in a file name kicking around. Or I’ll do a weird typo/premature enter and part of the file name will be treated like a -flag of some sort.

harsh3466 ,

Depending on the file it’s either dot notation or flat case.

Charadon ,
@Charadon@lemmy.sdf.org avatar

PascalCaseForTheWin

Monstera ,

Kebab for most things, camel for source code

31337 ,

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.

friend_of_satan ,

Related: a list and explanation of variable naming conventions pluralsight.com/…/programming-naming-conventions-…

MyNameIsRichard ,
@MyNameIsRichard@lemmy.ml avatar

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.

data1701d ,
@data1701d@startrek.website avatar

I do kebab with underscores.

MutilationWave ,

Wouldn’t that be snake?

jollyroberts ,

Snake Case and Pascal Case is what I tend to default to

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • lifeLocal
  • random
  • goranko
  • All magazines
    •