Was forced to code like this:

if(condition)
{
//code
}

Instead of this

if(condition){
//code
}

Also I should mention that this happened 4 years ago and my mentor (27 years old economy major at the time) did not know how to use git, we stored projects on a shared networking folder.

if its C# then I'd understand why forcing

{

}

But using a shared network folder is just too much to deal with ...

aeugh

To be fair I definitely prefer the former over the later. I find it much cleaner and gives a bit of a break between code lines.

But using network share drives instead of a repo is just gross

It's a good practice if the styleguide forces one of these styles to make the code base consistent.

What @gitpush said 🤨

First one ftw
tatata()
{
|
}
is clear and beautiful. Can easily find blocks limits without an IDE.

tatata(){
/
/
}
is a meaningless way to save lines or whatever. Totally unpractical.

Correct indentation should clearly show the code blocks.

I use codestyle of default IDE formating.

Write like a monkey, press ctrl+E,D (for visual studio) and you are done.

@NoToJavaScript doesn't work in some cases.

Scala can confuse intellij because it thinks its formatting java.

@cmarshall10450 True.

But works well for my stack : C#, HTML, SASS, TypeScript

Dude, in my company guys even don't know what is going on with versioning and they are just dragging and droping files on filezilla XD

I agree that the first way is better, at least in my opinion, but in the end it depends on the language and it's standards so when a new person comes in with different IDE settings or knowing the standards everything keeps working

>Not know how to use git
Leeaaaarrrnnnn, its fucking simple. God damn people that don't even try

Worst thing ever:
if (cond)
{
//Do stuff
}
else
if (cond2)
{
//Do other stuff
}
else
{
//Some more stuff
}

"This is better!"

"No, that is better!"

Use the standard your team uses, that's the important part.

Just configure your code formater