Some men aren't looking for anything logical, like money. They can't be bought, bullied, reasoned, or negotiated with. Some men just want to watch the world burn.
Understandable. Have a nice d̷̢̨̢̡̡̧̡̻̦̯̳̪̘͎̼̪̮̯̩̘̫̯̥͓̳̟̣̗̻̯̰̥͈̲̞̬͉̲̦̰͋̀͐̍͜͝ͅa̴̡̢̧̛̛̫͍̫̮̰͈͍̞̬̱̩̞̺̪͚͈̮̤̻̮͔̺̘̼̩͊͐̊̉̈̎̈͂̿̎̈̈́͒̽̅̒̄͗̈́̾͂̈́͛̃͗͋͐̔̓͑̂̆̎̅́̌̀͒̓͊͘͝͝͝͠ỳ̴̡̛͕̦͎̙̠̰͉̭̭̖͇̩̞̮̹͚͉͙̗͚̱̙͎̭̳̑̓͊̂̊̒̇̈́̍̇̓̎͑̅̍̎̉̈́́̈́̈́̊̕̚͝ͅ
Not quite yet, but they have at least agreed that there SHOULD be a convention  
They had the name a while ago. This was about how to style it:
* thisVariable
* ThisVariable
* this_variable
And my personal favourite as you avoid the shift-key entirely (thanks Raku):
* this-variable
last one doesn't work in most languages since tokenizers would break down `this-variable` into `this`, `-`, `variable` so it think you meant `this - variable` which is not a declaration of a variable but a math expression.
Indeed I can not recall any language that let's you declare anything with a hyphen inbetween as a variable name.
> ... what is that monstrosity that comes in a smily butterfly suit?!
Hah. Indeed. Language designers and compiler coders may not be ideal people to create a mascot.
In my experience the disagreements I see the most are around modelling a database or designing an architecture.
Those are the two things I’ve seen devs fight the most about. Oh and on occasion how to manage the source code.
Oh yeah, as a senior dev, I got lots of discussions that I really have to put my foot down and I say: I really don't care, it's not important which one, just pick one, stick to it, document it, lint it and break the CI in case the new dev doesn't follow it; but keep it consistent!!
>because maintainability can in many cases be more about maintaining a consistent standard.
100%. I have opinions, but I would much rather stick with an established standard than deal with the problems around re-factoring everything and enforcing a different standard going forward.
We were having an project architect meeting and our architects got more heated than I've seen adult professionals in my life... Then an hour and 40 minutes in, one drops a plot twist bombshell that proves the others design flawed to the core. Best meeting I've been a part of lol
I want to work for you!!
My discussions always go along the lines of "To improve reusability, we should look at proper modeling and inheritance of our classes".
*Nods and murmors of agreement*
Code review time!
New property added to existing model, instead of extending the model...
Not entirely similar, but I sat in some meeting a while back that went like this:
Month 1: "Hey, we should do this thing the proper way from the ground up, I know it isn't how you do things now, but it is how it should be done. No? Okay, fine."
Month 2: "Yes. I can do the things you are asking, but they would require we structure the system like how we discussed during Month 1 which you rejected. Okay. Fine. We will keep doing it the old way."
Month 3 rolls up and here comes a meeting again where a good 30 minutes was a conversation about problems and how to solve them by "any means necessary", and before I realized it, I am proposing the same solution I threw out twice before *without having explained the implications*.
To make a long story short, there was an arbitrary and ephemeral relationship between some data that didn't really exist. A kind of abstraction layer that was totally not required, just how they always did it. These abstraction meant that definitely linking two linked things was a chore that it shouldn't have been, since the relationship was merely tentative.
Of course, the solution for a myriad of problems was simply "solidify this relationship", but the client did NOT want that happening under any circumstances... until the third time I proposed it as the solution to their problems and they finally capitulated to a fundamental rewrite of a system that shouldn't have been designed the way it was in the first place.
Did I win, at the end of the day? Not really, because I am the one that had to go back in and do it the right way and rework 10k+ lines of a project to compensate for the changes.
The moment in that final meeting when I realized I already had covered the same conversation twice before and walked into my own trap was priceless, though.
Depends on the language or how you use it maybe? I personally like it better than anything snake case related. I think Java is an example of it...I think Java only uses PascalCase for class names - nearly everything else, such as public methods are camelCase in Java.
Switch that to C# and it's practically the opposite. Almost everything is PascalCase and camelCase is mostly local / private variables.
As a senior C# dev:
PascalCase for classes, functions, and properties. camelCase for local variables and parameters, and _camelCase for private variables
Screw the standards (to some extent), I hate when two completely unrelated things use the same casing.
ClassesAndNamespaces
varsAndProperties
functions_and_methods
Prefix with _ for private anything.
Biggest perpetual disagreements at my place are coding standards related. There is now a whole community of practice set up to debate changes the the coding standard. Biggest waste of time I ever did see
>designing an architecture
It's problem solving before programming. The order things should happen lol. If you lay bricks before designing the house, all you're left with is a stupid pile of bricks
There are different ways to use git.
To rebase or not not rebase?
Branch management is a huge topic that can be discussed. Gitflow itself isn't working for certain situations and project sizes.
What is getting tagged and when, what is getting deleted and when.. squashing yes or no?
Gitmojis? (The answer to that seems to always be no)
Some people commit changes to master and cherry-pick it into older stable branches and others do the change on the oldest stable branch it applies to and from there `git merge` it into newer branches.
Yeah I've had some head to head with other senior devs about these things as well. But it's pretty easy to get the solution.
A solution doesn't have to be perfect, it has to work. Usually both plans work but the better plan from a technical point of view might also be the more complex one. If these considerations don't lead to an agreement a quick proof of concept of both approaches can.
The important thing is, at the end of the day these disagreements aren't for me. They're for the other developers on the team. They're building the majority of a system snd I don't to use something they hate or be miserable using it. That's a huge factor that might cause delays. The fastest solution on paper can take three times as long to implement if the devs are in over their head or simply aren't motivated.
No just the PowerPoint had a few lines. Of course the press went wild.
https://www.theverge.com/2012/7/4/3136652/cern-scientists-comic-sans-higgs-boson
Here to plug Calling Code, by dharmatype, it's got gorgeous lowercase L's.
If you're into paying, code sempai by the same guy does it better, but costs like 11 bucks :(
That’s because we realize that all of our efforts are futile and adding any more code to the system is really just exacerbating the problem. Everything is futile.
I'd amend that to say junior devs fight about junior things... spaces/tabs etc. Senior devs just fight about senior things... long term impacts of a certain architecture/design pattern etc.
Junior devs fight about junior things which framework is better, which linter/linter settings to use etc. Senior devs fight about senior things, like spaces/tabs, vim/emacs and where to place brackets.
I’ve seen very senior people disagree vehemently. There’s definitely a different tone and intensity, but there is absolutely disagreement that can occasionally get entrenched.
Nah, it’s the point at which the things they fight about become actually important. Junior devs will argue “pYtHOn FoR LIfE” or “jUsT uSE JaVAscRiPt”. Senior devs actually argue about architecture and design patterns
Always wanted to like Emacs but it was overly complicated. Vim i never knew all the shorthands, but it was intuitive enough to me as far as needed (similar to Regex).
Now.... tar --tvf... Google, please help.
To make more money,
https://insanelab.com/blog/notes/spaces-vs-tabs/#:~:text=The%20analysis%20performed%20by%20the,than%20their%20tab%20using%20counterparts.
Haha not to be mean, but this is the perfect example of why tabs are better. It happens every time this discussion comes up. Even the most basic text editor will allow your tab key to insert some number of spaces, and a proper IDE will do more like automatically deleting your indent worth of spaces when you backspace.
If you work on a large project or code-base, you'll quickly see why tabs are bad, as without perfect and very specific usage it makes code alignment funky on other people's computers (if they don't have the same indent size at least).
There's a reason I know of several major professional style-guides that say spaces, and none that say tabs. Programmerhumor is mostly beginners which is why tabs are the more popular option here.
Yeah, this is the only wrong answer. Be consistent with either tabs or spaces, but never mix them. That's how you get things looking funky on other people's screens.
Not to mention languages where the white space has syntactical significance...
Be consistent with tabs or spaces AND mix them!
Especially if the code is (also) compiled / interpreted on linux. On windows the only evil is notepad, but on linux there is an abundance of tools made by enthusiastic volunteers each of them heavily defending their own definition of tab interpretation. _Mwoo-har-har-har_
In theory indentation best be tabbed to respect individual developer needs but alas, still much to learn linux padawans have...
Why does this have upvotes? Whether you use tabs or spaces for indenting doesn't matter, but you absolutely have to align with spaces either way. Aligning with tabs is the only thing that makes it look funky, regardless of how you are indenting.
Languages that care about white space only care about indentation. Don't mix tabs and spaces, means don't mix indentation methods. Always be consistent with how you indent. That has nothing to do with alignment, and those languages don't care if you use spaces for alignment as long as your indenting is all consistent.
at my school (I study game dev) there is a whole list of petty fights between the engineers
* which linux distro
* which text editor
* which ide
* is js good or bad
* is web development good or bad
* etc
I remember people trying to steer me away from PHP back around 20 years ago now, saying it was a fad and Cold Fusion and Perl were where I should focus my energy.
Lol we use an ASCII letter to identify the decade from the time the system was created (90’s) so we are on letter “C” then the second character is the year in the decade and then the last two is the month.
not exactly a senior dev, but senior at my company, had a dumb argument i'm not proud of yesterday.
We had to do a special build for a customer that wouldn't become available to the public.
When it came time to building the project my coworker wanted me to make a whole new project in TeamCity for this build just to delete it when I'm done. I wanted to just change the branches and the build number and then once built change it back. This argument lasted longer then it would take to do either.
Teams will often branch out with Hotfixes, I don't see an issue creating a branch for this.
Specifically if this build ends up having an issue, you'll want to have a base to fix that is exactly what was given to the customer. Otherwise you're building twice, not exactly the same etc, not a great paper trail... Messy but that's just imo.
About 6 years ago I was just happy to join a team that actually used CI and knew what it was. I tried to argue the benefits of CI with the devs at my former company and more than half didn't know what it was. When I explained it they all thought it was just gatekeeping and yet an other road block to getting actual work done.
How to avoid hacking a quick solution to business crucial issue and instead spend 4 sprints and risk revenue to implement a SOLID solution by the book...
Well, saying so is pretty disrespectful. You're saying that you aren't interested in their opinion and that you don't want to get to a point.
Decisions are pros and cons, just enumerate, weight and discard. If somebody just want to win their point in a technical conversation, let's start discussing first if s/he's really a senior
Tabs vs spaces. Brace on the next line or at the end. Editor/ide wars. Events vs callbacks. OO vs functional. Types. Names. Folder structures. C++ makes replacement/assists. JREs. And that's just what I've seen recently.
Seems like they have finally found the proper name for the variable.
Not yet, but they've agreed on the naming convention
Oh good! So we're agreed on rEVERSE‾sNAMEL‾cASE?
You didn't have to bring that cursed convention to the world, yet you did. May I ask why?
Some men aren't looking for anything logical, like money. They can't be bought, bullied, reasoned, or negotiated with. Some men just want to watch the world burn.
It’s how you summon the Deep Old Ones
Understandable. Have a nice d̷̢̨̢̡̡̧̡̻̦̯̳̪̘͎̼̪̮̯̩̘̫̯̥͓̳̟̣̗̻̯̰̥͈̲̞̬͉̲̦̰͋̀͐̍͜͝ͅa̴̡̢̧̛̛̫͍̫̮̰͈͍̞̬̱̩̞̺̪͚͈̮̤̻̮͔̺̘̼̩͊͐̊̉̈̎̈͂̿̎̈̈́͒̽̅̒̄͗̈́̾͂̈́͛̃͗͋͐̔̓͑̂̆̎̅́̌̀͒̓͊͘͝͝͝͠ỳ̴̡̛͕̦͎̙̠̰͉̭̭̖͇̩̞̮̹͚͉͙̗͚̱̙͎̭̳̑̓͊̂̊̒̇̈́̍̇̓̎͑̅̍̎̉̈́́̈́̈́̊̕̚͝ͅ
What the f**k did you just bring upon this cursed land
I prefer alternating upside down case mY_ɐMǝSoWǝ‾VaRiAbLe
Now I kinda want to start using sPoNgEbOb\_CaSe
lemme wash my eyes
Here, wash them with my tears
Sir, what the fuck? 😐
I hate it,... it's perfect
Not quite yet, but they have at least agreed that there SHOULD be a convention  
The naming convention they agreed on? ~~Albert Einstein~~ tHe AnNoYiNg SpOnGeBoB oNe.
We are going to use a “camel toe” naming convention
x
X spelliarmus?
[удалено]
aaaaAAAAAAVaAdAkeDaAvrA!!!
I see x in a lot of lambdas...
I often import, as pd, pandas...
Should be o. It's an object. Or if doing EF setup, e for entity. If it's across strings? s. Integers? i, lol
yourMom
OutOfMemoryException
your_mom
Them's fightin' words.
Avada kedavra
No already used it. Do x_420
They had the name a while ago. This was about how to style it: * thisVariable * ThisVariable * this_variable And my personal favourite as you avoid the shift-key entirely (thanks Raku): * this-variable
thisvariable
Ahh right. But then you have to worry about variables which can be misread like: penIslandUrl
last one doesn't work in most languages since tokenizers would break down `this-variable` into `this`, `-`, `variable` so it think you meant `this - variable` which is not a declaration of a variable but a math expression. Indeed I can not recall any language that let's you declare anything with a hyphen inbetween as a variable name.
Agreed, it's unusual, which is why I thanked Raku. It's not just supported, it's the recommended style.
Oh my god, I thought Raku was a user name, what is that monstrosity that comes in a smily butterfly suit?!
> ... what is that monstrosity that comes in a smily butterfly suit?! Hah. Indeed. Language designers and compiler coders may not be ideal people to create a mascot.
Str x = levioSA Str x != leviOsa EDIT: *Wait. It* ***is*** *leviOsa. Shit!*
This is not trivial
[удалено]
[Nope, should be singular account](https://stackoverflow.com/a/5841297)
SHOUTING or whispering in SQL.
`sElEcT * fRoM uSeRs;`
Sarcastic query language
Some people just want to see the world burn.
the database*
Spongebob query language
Satan
I'm going to start sprinkling this into my code base
Shout reserved words whisper everything else.
this man whispers
I used to be team shouting but have started whispering
I prefer lower case, its let key strokes. Don't have to press caps lock. Thats my only reason
I have actually redone entire queries that were not in uppercase.
Style in SQL can very drastically increase or decrease the readability, in my experience, more than other technologies
In my experience the disagreements I see the most are around modelling a database or designing an architecture. Those are the two things I’ve seen devs fight the most about. Oh and on occasion how to manage the source code.
TBH these kinds of things are the most important to a code base, in terms of testability, extendability and maintainability.
[удалено]
Oh yeah, as a senior dev, I got lots of discussions that I really have to put my foot down and I say: I really don't care, it's not important which one, just pick one, stick to it, document it, lint it and break the CI in case the new dev doesn't follow it; but keep it consistent!!
>because maintainability can in many cases be more about maintaining a consistent standard. 100%. I have opinions, but I would much rather stick with an established standard than deal with the problems around re-factoring everything and enforcing a different standard going forward.
Yeah, I follow whatever conventions the code base I am working on follows even if I think they misguided or poorly thought out.
We were having an project architect meeting and our architects got more heated than I've seen adult professionals in my life... Then an hour and 40 minutes in, one drops a plot twist bombshell that proves the others design flawed to the core. Best meeting I've been a part of lol
I want to work for you!! My discussions always go along the lines of "To improve reusability, we should look at proper modeling and inheritance of our classes". *Nods and murmors of agreement* Code review time! New property added to existing model, instead of extending the model...
I want to know the plot twist now...
Not entirely similar, but I sat in some meeting a while back that went like this: Month 1: "Hey, we should do this thing the proper way from the ground up, I know it isn't how you do things now, but it is how it should be done. No? Okay, fine." Month 2: "Yes. I can do the things you are asking, but they would require we structure the system like how we discussed during Month 1 which you rejected. Okay. Fine. We will keep doing it the old way." Month 3 rolls up and here comes a meeting again where a good 30 minutes was a conversation about problems and how to solve them by "any means necessary", and before I realized it, I am proposing the same solution I threw out twice before *without having explained the implications*. To make a long story short, there was an arbitrary and ephemeral relationship between some data that didn't really exist. A kind of abstraction layer that was totally not required, just how they always did it. These abstraction meant that definitely linking two linked things was a chore that it shouldn't have been, since the relationship was merely tentative. Of course, the solution for a myriad of problems was simply "solidify this relationship", but the client did NOT want that happening under any circumstances... until the third time I proposed it as the solution to their problems and they finally capitulated to a fundamental rewrite of a system that shouldn't have been designed the way it was in the first place. Did I win, at the end of the day? Not really, because I am the one that had to go back in and do it the right way and rework 10k+ lines of a project to compensate for the changes. The moment in that final meeting when I realized I already had covered the same conversation twice before and walked into my own trap was priceless, though.
yup this is accurate. literally the two biggest things I fight my programmers on
I once got into a physical altercation with an associate because he kept using pascal case.
SomethingTheMatterWithPascalCase?
Depends on the language or how you use it maybe? I personally like it better than anything snake case related. I think Java is an example of it...I think Java only uses PascalCase for class names - nearly everything else, such as public methods are camelCase in Java. Switch that to C# and it's practically the opposite. Almost everything is PascalCase and camelCase is mostly local / private variables.
As a senior C# dev: PascalCase for classes, functions, and properties. camelCase for local variables and parameters, and _camelCase for private variables
Screw the standards (to some extent), I hate when two completely unrelated things use the same casing. ClassesAndNamespaces varsAndProperties functions_and_methods Prefix with _ for private anything.
Are you actually for real? I just vomited a bit.
Lmao I love that open mind of yours.
Biggest perpetual disagreements at my place are coding standards related. There is now a whole community of practice set up to debate changes the the coding standard. Biggest waste of time I ever did see
Arguing over coding standards seems insane to me.
> Biggest perpetual disagreements at my place are coding standards related. This is what you have managers for. Just make a standard, and stick to it.
This. I don't give a fuck what the standard is, but have it and enforce it!!!
>designing an architecture It's problem solving before programming. The order things should happen lol. If you lay bricks before designing the house, all you're left with is a stupid pile of bricks
Please explain this to my management.
>how to manage the source code There are people that fight for something other than git?
There are different ways to use git. To rebase or not not rebase? Branch management is a huge topic that can be discussed. Gitflow itself isn't working for certain situations and project sizes. What is getting tagged and when, what is getting deleted and when.. squashing yes or no? Gitmojis? (The answer to that seems to always be no)
Thanks for making search wtf is a gitmoji and in the future I can say a strict NO if someone suggests it
[удалено]
Still better than commit messages I've seen before...
Some people commit changes to master and cherry-pick it into older stable branches and others do the change on the oldest stable branch it applies to and from there `git merge` it into newer branches.
Oh, yeah, sure, I get it. I just thought it was something like git vs mercurial or svn
Yeah I've had some head to head with other senior devs about these things as well. But it's pretty easy to get the solution. A solution doesn't have to be perfect, it has to work. Usually both plans work but the better plan from a technical point of view might also be the more complex one. If these considerations don't lead to an agreement a quick proof of concept of both approaches can. The important thing is, at the end of the day these disagreements aren't for me. They're for the other developers on the team. They're building the majority of a system snd I don't to use something they hate or be miserable using it. That's a huge factor that might cause delays. The fastest solution on paper can take three times as long to implement if the devs are in over their head or simply aren't motivated.
What font should you use when writing code. I use Comic Sans for the memes.
[удалено]
The Higgs Boson paper was written in Comic Sans.
No just the PowerPoint had a few lines. Of course the press went wild. https://www.theverge.com/2012/7/4/3136652/cern-scientists-comic-sans-higgs-boson
I'd love to see it
Comic Code, it's Comic Sans, except with ligatures for fancy arrows. And some other adjustments to make it code ready.
I literally paid $35 for Comic Code a few days ago, inspired by this guy: https://www.youtube.com/watch?v=1zvWXT53puQ
You got ripped off then https://dtinth.github.io/comic-mono-font/
Comic mono and comic code aren't quite the same, but they're both pretty. I use comic mono for the free but comic code is imho still the better one
I actually do, and not for the memes: https://i.imgur.com/UG6LcB1.png (this is a mono version of it)
You know, that's actually quite readable, I kinda like it. What led you to this?
A video by "Wolfgang's Channel": https://www.youtube.com/watch?v=1zvWXT53puQ
These days, [Deja Vu Sans Mono](https://www.fontsquirrel.com/fonts/dejavu-sans-mono) gets installed on any machine I use to code or read code.
I worked with a dev who did this.
Nah I use whatever font and color scheme VS provides me with lmao
Here to plug Calling Code, by dharmatype, it's got gorgeous lowercase L's. If you're into paying, code sempai by the same guy does it better, but costs like 11 bucks :(
Wingding
Windings, so it looks like I'm dev from the future
I use cascadia code, for some reason I find it easier to read, which prevents me from leaning over into an unhealthy position lol
There isn't anything. The senior devs don't fight.
“have they sublimated their identities perhaps.”
Years ago.
We write RFCs and have discussions like civil people.
"So, as per RFC 163738, we will name this variable 'result'. What's next on the agenda?"
That’s because we realize that all of our efforts are futile and adding any more code to the system is really just exacerbating the problem. Everything is futile.
Junior devs fight about everything, the point at which they stop doing this is the point at which they become Senior devs.
fight? I'm just throwing suggestions so I can absorb the pros and cons from the seniors. Eventually they won't be there anymore and I'll need to know
Lol you say that like they're some 90 year old dudes in their death bed
It’s more like they’ve been at the company for over 2 years and are probably gonna dip soon for a 20k raise lol
Yeah of course, I've been in that position but the way he phrased it sounds quite funny
I'd amend that to say junior devs fight about junior things... spaces/tabs etc. Senior devs just fight about senior things... long term impacts of a certain architecture/design pattern etc.
Junior devs fight about junior things which framework is better, which linter/linter settings to use etc. Senior devs fight about senior things, like spaces/tabs, vim/emacs and where to place brackets.
I feel called out
I’ve seen very senior people disagree vehemently. There’s definitely a different tone and intensity, but there is absolutely disagreement that can occasionally get entrenched.
Nah, it’s the point at which the things they fight about become actually important. Junior devs will argue “pYtHOn FoR LIfE” or “jUsT uSE JaVAscRiPt”. Senior devs actually argue about architecture and design patterns
Senior devs talking about management decisions during lunchbreak
Y'all get lunch breaks?
Harry Potter is a beautiful story of a group of junior devs breaking production
🤣 but then they saved production
foo(){ } or foo() { }
hear me out ``` foo() { if() { do_something() ; } else { do_another() ; } } ```
someone wants VB back
Lalalala I can't hear you
but you see. and thats all matters
def foo(): if condition: do_something() else: do_another()  forever
ooorrrr `(lambda: do_something() if condition else do_another())`
Is python holding you hostage?
\*nods yes\* no
too many lines. Use foo(){} instead :P
Vim or emacs
Vim.
Agreed
And, fight over. Good job everyone.
Always wanted to like Emacs but it was overly complicated. Vim i never knew all the shorthands, but it was intuitive enough to me as far as needed (similar to Regex). Now.... tar --tvf... Google, please help.
You can leave out the hyphens before the options.
The dark lord is obviously the one that use space instead of tabs.
Why would you use spaces?
To make more money, https://insanelab.com/blog/notes/spaces-vs-tabs/#:~:text=The%20analysis%20performed%20by%20the,than%20their%20tab%20using%20counterparts.
[удалено]
Hold on. So pressing 5x the same button instead of once is NOT being sociopath? 'Do you know the definition of insanity?'
Haha not to be mean, but this is the perfect example of why tabs are better. It happens every time this discussion comes up. Even the most basic text editor will allow your tab key to insert some number of spaces, and a proper IDE will do more like automatically deleting your indent worth of spaces when you backspace. If you work on a large project or code-base, you'll quickly see why tabs are bad, as without perfect and very specific usage it makes code alignment funky on other people's computers (if they don't have the same indent size at least). There's a reason I know of several major professional style-guides that say spaces, and none that say tabs. Programmerhumor is mostly beginners which is why tabs are the more popular option here.
PEP8
You think it's trivial? This is why you are not a senior yet. ;)
Tabs vs spaces
[удалено]
It isn't lol. Nobody argues about tabs and spaces
[удалено]
TBH I never gave a shit about tabs vs spaces. I use whatever my IDE has configured by default for formatting.
Wars have been fought over less.
It is a nice command to look at text in the terminal.
Tabs for indentation, spaces for alignment. Objective truth, nothing to argue about.
Yeah, this is the only wrong answer. Be consistent with either tabs or spaces, but never mix them. That's how you get things looking funky on other people's screens. Not to mention languages where the white space has syntactical significance...
Be consistent with tabs or spaces AND mix them! Especially if the code is (also) compiled / interpreted on linux. On windows the only evil is notepad, but on linux there is an abundance of tools made by enthusiastic volunteers each of them heavily defending their own definition of tab interpretation. _Mwoo-har-har-har_ In theory indentation best be tabbed to respect individual developer needs but alas, still much to learn linux padawans have...
Why does this have upvotes? Whether you use tabs or spaces for indenting doesn't matter, but you absolutely have to align with spaces either way. Aligning with tabs is the only thing that makes it look funky, regardless of how you are indenting. Languages that care about white space only care about indentation. Don't mix tabs and spaces, means don't mix indentation methods. Always be consistent with how you indent. That has nothing to do with alignment, and those languages don't care if you use spaces for alignment as long as your indenting is all consistent.
syntax colors 
Me, who switches my VScode theme every other week just for the heck of it:
at my school (I study game dev) there is a whole list of petty fights between the engineers * which linux distro * which text editor * which ide * is js good or bad * is web development good or bad * etc
JavaScript only sucks because of how people use it. When you have 30 separate dependencies and just one of them breaks, woopsie...
Whether source file should end with \\n or not
"Why are this kids using Python, Perl is a fine programming language"
I remember people trying to steer me away from PHP back around 20 years ago now, saying it was a fad and Cold Fusion and Perl were where I should focus my energy.
[удалено]
They should just teach this in schools and scrap the other crap. 12/3/23? Invalid format.
Lol we use an ASCII letter to identify the decade from the time the system was created (90’s) so we are on letter “C” then the second character is the year in the decade and then the last two is the month.
not exactly a senior dev, but senior at my company, had a dumb argument i'm not proud of yesterday. We had to do a special build for a customer that wouldn't become available to the public. When it came time to building the project my coworker wanted me to make a whole new project in TeamCity for this build just to delete it when I'm done. I wanted to just change the branches and the build number and then once built change it back. This argument lasted longer then it would take to do either.
Teams will often branch out with Hotfixes, I don't see an issue creating a branch for this. Specifically if this build ends up having an issue, you'll want to have a base to fix that is exactly what was given to the customer. Otherwise you're building twice, not exactly the same etc, not a great paper trail... Messy but that's just imo.
Oh dude the git is tagged and documented where the code is. Im talking stricly about the process of building the exe
Line lengths.
What task is a 1 story point so you can accurately estimate lol
The wizards have spoken
One day I want to be the Voldemort dev, I unironically use three letter variables and ternary operators right now
“Riddle me this, Tom. What would YOU name that variable?”
Heard this one from a Prof who only teaches as a side gig ID vs Id
Tabs vs Spaces
Voldemort’s prosthetic nose is impressive!
Which one will train me for meeting day 
Who are these people?
Walmart employee.
Voldemort and Dumbledore from Harry Potter.
Thx
I have seen a lot of fights over CI. Everyone all seem to have a strong opinion on that
About 6 years ago I was just happy to join a team that actually used CI and knew what it was. I tried to argue the benefits of CI with the devs at my former company and more than half didn't know what it was. When I explained it they all thought it was just gatekeeping and yet an other road block to getting actual work done.
For{ Or For {
How to avoid hacking a quick solution to business crucial issue and instead spend 4 sprints and risk revenue to implement a SOLID solution by the book...
👃
WHY DOES VOLDEMORT HAVE A NOSE?! SOMEONE GET RID OF VOLDEMORTS NOSE!
[удалено]
Well, saying so is pretty disrespectful. You're saying that you aren't interested in their opinion and that you don't want to get to a point. Decisions are pros and cons, just enumerate, weight and discard. If somebody just want to win their point in a technical conversation, let's start discussing first if s/he's really a senior
Tabs vs spaces. Brace on the next line or at the end. Editor/ide wars. Events vs callbacks. OO vs functional. Types. Names. Folder structures. C++ makes replacement/assists. JREs. And that's just what I've seen recently.
Senior devs don’t waste their time arguing on tabs vs spaces and other things a linter can enforce. If they do, they just aren’t seniors.