It heavily depends on the context: Filenames? Variables? Functions? Interfaces/Classes? Java? C? Shell?

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.

This question just shows how messed up, and broken much of IT is.

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

IWRITELOTSOFBASH

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.

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.

If it’s something that will be mostly interacted with over CLI then kebab case. If GUI then spaces

I generally end up using snake case.

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.

Snake if writing in python

Camel if writing in PowerShell

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

code: camel or snake, depending on language

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

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

My file

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

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 😥

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.

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.

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

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 don't have a consistent style for everything and it depends on the circumstances. snake_case is often used, especially to avoid spaces. Sometimes I just do flatcase instead, and in rare cases also kebab-case or combined_snake-and-kebab-case. The combined_case is often useful to group parts of the name, like a dates and version numbers together and to indicate what part is constant; example-name_2024-08. Sometimes I also do the "Title Case", which is basically PascalCase, but with spaces. Or even even more weird, "Python_Case", which is PascalCase, but with snake_case, when I want to avoid spaces.

I often avoid dots in regular filenames, unless they indicate a file extension or format, such as ".svg" and ".inkscape.svg" to indicate its a specific version of the SVG format. Or ".xiso.iso", as a specific compressed version of the regular ISO file (for use with Xemu emulator). Basically the same logic and tradition as ".tar.gz" (but in reverse order).

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

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

PascalCaseForTheWin

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

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

Snake case and kebab case mixed arbitrarily.

stOcHaStIC-l33t-CasE FTW yizzo.