The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
A long time ago I made a very primitive webpage to collect my bookmarks. It has a background image, a title image, and a table of two columns with all of the links. I have used this page for about twenty years to hold my frequently visited links and it has worked fine with every browser I have tried it on this entire time except for Edge.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
I burst out laughing when I read that. You are so right on the mark there!
The everlasting struggle of developers and naming stuff...
I'm not quite happy with my current project names (they're a bit longish, Company.Domain.Project.Data, for example), but what's bothering me even more at the moment is my own naming convention in Azure.
I prefer PascalCased, like ThisIsMyWebApp, which is fine, except for other resources, like a SQL Server, which only allows lower characters.
Long story short, I now have:
I'm now leaning more towards my-sql-server style for everything unless -'s are not possible, like with storage accounts.
If this is what I'm worrying about everything must go pretty well, and it does, but this kind of stuff bothers me more than it should
I'll take an F.
I'd like to buy a vowel Pat, U!
I'd like to solve that Puzzle Pat...
Sorry, could NOT resist.
On the topic, I often throw a little slang around when I get bored with naming. An example would be a module I wrote to get domain whois data. I named the function "WhoIsDis" and another "WhoIsDat" for the string data received.
I've always preferred the underscore and all lowercase like my_web_app and my_sql_server...kind of a pain with the added shift, but eventually muscle memory kicks in. I know this is against sql server best practices, but I don't follow stupid rules.
Sander Rossel wrote:
like a SQL Server, which only allows lower characters.
I don't like underscores, they're kind of a throwback to the pre-2000's last resort
PascalCasing for classes, methods and properties in C# and SQL, camelCasing for variables and Java(Script), this-type-of-casing in HTML and CSS (and now Azure too I guess), this_kind_of_casing only when I have no other option or if that seems to be the standard in the project I'm working on and thiskindofcasing only for Azure storage accounts because that only allows lower case characters for some reason.
I also never use THIS_SORT_OF_CASING, constants just get regular PascalCasing.
And fields aren't prefixed with an _underscore.
Azure simply doesn't allow upper case characters in a SQL Server name (I'm talking about the SQL Server resource, not the actual database).
Only lower case characters, numbers and -'s, so sqlserver1 and sql-server1 are alright, but SqlServer is not
I typically use underscores as lead ins for private members in .NET classes and structs.
The reason being is because .NET/C# will not let you declare two members of the same name at different protection levels. Leading with an underscore prevents naming conflicts with protected, public or internal members used in derived classes.
Other than that, I feel the same way you do about them.
The other exception is when i'm working in an environment where everything is named like that. When in Rome...
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.