Linux

I like snake, but in some interfaces the underscores blend into the text line or are not rendered properly, so it becomes eaaier to discern if the filename has spaces or separators by using kebab.

Depends. Java-like languages ofc camel/pascal case.
Bash, Python, etc., snake case, with constants as uppercase.
Filenames: I prefer snake case.

IWRITELOTSOFBASH

Both snake and camel case. Sometimes I mix it in the same project and I hate myself for it

Pascal_Snek_Case

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.

Whatever case I get when my finger reaches the shift key.

General purpose: Kebab case

But really, follow the conventions of what you're working on. For example, I'd use pascal case when working on a Java/Kotlin project, and snake case when working on a Python project.

I've got one more to add to your list, and I hate it, but it's worth mentioning: https://en.m.wikipedia.org/wiki/Hungarian_notation

It's when the data type is in the name of the variable.

For files, date+Snake: 20240831Letter_to_Rodney.odt For variables, Screaming

I generally end up using snake case.

I kebab case mine for personal files.

It's mostly because I don't have to use a modifier key and it's doesn't need url encoding and all in the same lowercase. Dot notation looks nice but I feel like dots are for extensions only. Flat case is horrible to read, screaming case even worse, camel/pascal case to many times ends up as coolFileNAme on first time typing.

I've done a couple of different styles because of programming in different languages but now if I have to do anything that's not kebab case I make a small frown.

I don't like it but I am used to reading old C codebase (windows: https://learn.microsoft.com/en-us/windows/win32/stg/coding-style-conventions) with Hungarian notation.

pszMyString 😥

My file

Camel case for short names snake case if it starts getting hard to read

code: camel or snake, depending on language

files/dirs: snake + kebab + dot mixture (trying to avoid caps and special chars here)

Have been defaulting to kebab case for variable and function names in all languages recently because of cargo yelling at me

Pascal case for class names cause c#, snake case for python files because it doesn't like kebab

Screaming case for env files because that's what everybody else does

I go with the "quotation case", "Cool file name".

Snake if writing in python

Camel if writing in PowerShell

I tend to stick with what the language wants me to use.

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

Snake case and kebab case mixed arbitrarily.

Snake case or kebab case I guess. But why is it called kebab case?

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

stOcHaStIC-l33t-CasE FTW yizzo.

Snake case for all kinds of file names and camel case for programming

PascalCaseForTheWin

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

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.

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.

1337 case = k3wlf1l3n4m3