Oof. This is a pet peeve of mine.

As manager, I shut this conversation down via direct messages to each team member involved.

I remind them that they agreed during retro to live with the current set of decisions for exactly two weeks until next retro.

I don’t dictate much, but I do dictate that Slack isn’t an acceptable place for this kind of discussion, on my team.

The only related thing, that belongs in slack, on my team, is a link to the current accepted team standard - which will be open for review and changes again during next retro.

Alternately, if there’s no strandard for this yet then my team knows they’re encouraged to wing it until we discuss at next retro.

And yeah, I’ve had to open an issue to revisit a variable name after retro, lol.

My team are an opinionated bunch, and they’re often perfectionists.

Camel_Case

I don’t get this meme at all… What am I expected to see in this picture? Or how am I supposed to interpret it?

I’ve found the origin and an explanation, and I think I do get what message this meme should convey, but I’m still confused.

I just use UUIDs

Let me tell you: I’m currently developing a user-defined, recursive form, and most of the trouble with that stems from the fact that I don’t have a good name for the repeatable part of that form (as opposed to a static part) and the thing the form is embedded in.

Variable names do matter.

happyMondaysMyAss

I’m just gonna say it: fuckYourCamelCase

One day I will see this drama… Until then, it will remain only in memes.

$goddamnitJeffStopChangingMyFuckingVariableNames = 1;

Missed opportunity to title post in the style of bad variable name.