When I start a project, one thing that comes to mind is naming it. Though, I am very particular about the casing.
Title Casing
… which is typically that. Not cased like a sentence, but like a name. Except it isn’t a person’s name. It is just… a title. But it has different rules depending on your preference in lover.
What is a title? I call myself the curator of-things. But shouldn’t that be the Curator of-Things? I don’t use title case for sections/headings.
Funny thing. As a whelp, I didn’t understand how capitalization was supposed to work for a while. On the chat interface I’d Type Like This and nobody was to tell me something about it. I don’t call myself a writer, but I think I understand it now. I like to think…
kabab-casing
The standard casing for npm packages. It’s probably where I started using italics.
For a while, I did use inline code formatting to denote package names. But when it came to my own projects, I started to use italics. And then used italics elsewhere.
Sentence casing
Cased like a sentence. This seems particularly weird to use for something like a name. Yet, I’m finding that I’m choosing to case my projects using this style. Again, using italics to denote names.
I think that I picked this off from DeArrow, a browser extension that uses crowdsourced titles for making YouTube videos less “clickbait.”. Submitters are required to submit titles using it as the extension is able to apply different casing styles consistently. It’s an in-joke to be “pipelined” into using sentence casing outside of DeArrow. And I think I have been. I don’t submit titles, I just browse YouTube with titles formatted as sentence case.
camelCase (and friends)
I have a very particular rule about using camelCase and its friends. Best way to describe it is: “if there was a space added before each capital letter, how would you case that name?”.
A given is a word like “API.”. It’s an acronym. But I find it confusing when more words like it are put into the mix. Something like… “APIManager.”. Typically, I would expand acronyms as part of my æffective coding style. But some acronyms are rather meaningless and come off as confusing when they are. Full Legal Name ApplicationProgrammingInterface.
To explore this idea, I developed the space Camel extension for Visual Studio Code. This simply adds a space to each uppercase letter that has a lowercase letter before it. “API” would be rendered as “A P I.”. Which I think isn’t a bug if the point is to write consistent names.
You’re welcome, “PhpApiHandler.”.