FUCK MY BOSS WHEN HE SAYS HE DIDNT SEE ANY UI CHANGES AFTER NOT SLEEPING FOR 24HRS TO GET THE ENTIRE BACKEND REWRITE DONE. I WENT OVER THE ACTUAL CHANGES WITH HIM 100 FUCKING TIMES! I GET THIS MESSAGE AFTER FINALLY GRABBING SOME FOOD "What did you do, you said you were going to work on the site??" FUCKFUCKITYFUCKFUCK!!! FUCK YOUR MONEY AND YOUR JOB!!!! AND WHILE IM AT IT FUCK WEBDEV!!! 🖕FUCK YOU GUYS🖕 IM GOING HOME

/rant Thank God for devRant

Kebab case kills me😂

My chewing algorithm needs improvement. Almost choked eating a fucking kebab.

We currently have multiple exercises for a lecture and they decided to use python this year instead of Matlab, but the codestyle is all over the place. Everything is yellow in my IDE and warnings everywhere.

Arghhh 😭

Trying to develop on Windows when you use Linux....

My desk buddies have a new friend! Thanks everyone!

On another note, @dfox has over 10k ++ now!!!

When your coworker brings in a mechanical with blue switches...and there's no headphones

Thanks guys for the great app and the stickers! @trogus @dfox

Netbeans is like the girl you pull at 3am in the kebab shop. You wouldn't brag about it, its bloated and bug ridden but it gets you there without having to shell out any more money.

all of them. countless wasted hours.

as fate decided to turn me from $random-dev-geek into "the guy that calls the shots in tech", one of my earliest decisions was to automate formatting.

everywhere, automated at CI.

gofmt was an inspiration for the industry.
js?/ts? use prettier
C++? use ClangFormat
etc.

always default settings.
enforced by pre-commit hooks and CI.

never a single argument about bracket style, I don't care if someone likes single or double quotes better.

"fucks given" counter is fixed at 0.
everybody prefers it (ok, sometimes after a while sometimes)

of course there is still some more conventions to do for us humans.
IMHO the most critical ones.

like naming or even casing (camel, snake, kebab, - which one works where), but taking out most of the "so what" decisions takes discussions to a much more resonable level.

Whenever I hear or see someone talking about Kotlin I immediately start thinking of Kotlets and Kebab and I get really hungry...

Best case name:
[ ] PascalCase
[ ] camelCase
[ ] snake_case
[ ] kebab-case

who-the-hell-thought-of-calling-this-kebab-case !! 🍖 😂

Working on implementing a new networking layer for business security requirements...but the requirements were talked about in backdoor "special" meetings; "lowly" implementation engineers aren't allowed in. God knows the engineers implementing the solution don't need to know requirements for what they are implementing 🙃

"Just encrypt everything!"
Oh sure let me just pull out my magic button 🤬

I've been trying to get a middle-healthy lifestyle (means I eat what I want while it's quality and not harmful, doing sports four times in a week, and stuff...) and actually I'm just waking up at a friend's home after a party where we just ate like two big fat cheesy French fries steak and cordon bleu European tacos (they look like a kebab, not Mexican stuff at all) asking myself where my self estime is.

Being a developer and loving to eat is really punitive sometimes...

Doing someone else's Code Review in my project: "You must retain the holiness and piety of the code you write by following PascalCase naming for files and kebab-case naming for CSS variables. Avoid using duplicate strings by declaring enums in a constants.ts file and using that all throughout the app"

During my own Code Review in someone else's project: "WHAT THE FUCK DO YOU MEAN I CANNOT PASS FUNCTION REFERENCES AS PROPS TO A REACT COMPONENT AND ALWAYS NEED TO INVOKE IT INSIDE AN INLINE FUNCTION FOR THE PROP."
"WHAT KINDA FKIN DRUGS ARE YOU ON TO USE snake_case IN TYPESCRIPT DID YOUR MOM DROP YOU ON YOUR HEAD WHEN YOU WERE BORN YOU SACRILEGIOUS PIECE OF SHIT"
"WHAT DO YOU MEAN I SHOULD USE BOTH SINGLE AND DOUBLE QUOTES FOR IMPORTS AS PER LOCAL OR GLOBAL; I'LL SHOVE THE SINGLE QUOTE UP YOU WHERE THE SUN DOESN'T SHINE YOU FKIN DEGENERATE MORON"

As much as I do believe in self righteousness of my own coding conventions over others (I might be slightly better than others but I really can't claim good authority because I've had my lapses in conventions too; and being one of the newer members of the team certainly doesn't help, despite my boss supporting my initiative), I guess it is high time we bring in some already established code conventions in the team that is finally big enough to warrant them. Maybe AirBnB.

so some controversial opinions

Our company is moving most of our code style to snake_case, even the JavaScript. Here's our resoning:

Take the CustomerAccountMembership model. In our Python server, we would access it as obj.customer_account_membership, in JavaScript as obj.customerAccountMembership and our API endpoint as api/path/customer-account-membership. Thus we had several String utility functions such as `camelize`, `kebabChop` (which is ironically camelCased) and `snakeify`, and we would use them in translating from URL path to JS to Python, which was troublesome.

Now HTTP allows _underscores_ unescaped and do not pose any significant meaning. JavaScript also accepts it as a valid character in variable names. On the other hand, HTTP is strictly lower-cased, and all computer languages use the -dash- to signify subtraction. Sooo the _underscore_ is the only style that is compliant everywhere.

Unless, of course, we go with customeraccountmembership, which I refuse to do.

I'm not that deep into code character rules.
Opinions?

Sitting in the kitchen by myself, headphones in, eating my Kebab, fondling on my phone, minding my own business. Of course I want to talk about your project I'm not even remotely involved in

Imagine that I have written 1000 lines of code and imported many libraries. Sometimes I get confused when trying to use a name I defined earlier. In my mind is this name a class or a method, is it a local or global variable, is this a constant. So I came up with a way and it totally works, although my ide complains, but who cares, I use it anyway.
I use PascalCase for class.
camelCase for methods.
snake_case or lowercase for global variables.
kebab-case I don't use this
UPPER_CASE for constants
snake_caseL or lowercaseL with a capital letter L at the ending for local variable.
I hope this is helpful 😊🤔

Everytime someone says kebab-case I get cravings for kebab.

Seriously, what's with the naming ordeal?
We start with userInput, then spiral into userInputUpdatedFinalV2

Are we writing code or crafting spell incantations? camelCase, snake_case, kebab-case, PascalCase – it's a syntax battleground.

Can we have names that make sense, for sanity's sake?

Starting new job, moving to new location, and trying to finish five massive projects.... "You want me to take over development of that entire stack? Sure I've got time!"