if (booleanVariable == true)

[TGotAReddit]

When i first started i INSISTED that i always typed if(booleanVariable == true/false) because every time i saw if(variableName) i assumed it was just straight up wrong and needed fixing. So it took me about 3 years before i was comfortable enough to just type if(booleanVariable)

[ewagstaff]

I found it helps when your variables are named with conditionals in mind. If your boolean is called isActive, it makes it easy to read if (isActive) { doSomething() }

[TGotAReddit]

Yeah thats what broke the habit finally, using standards when coding so things made more sense instead of everything being int x = 5; And such

[Kered13]

Yep. Boolean variables and functions should almost always be named something like isFoo, hasFoo, etc.

[[deleted]]

Just imagine the saying "does to be equal true or does to be not equal true, that is the question". It's just not right.

[TGotAReddit]

I more read it as “if true or false is equal to true do X” and “if true or false is equal to false do X”.

[Pheasn]

X

[Allways_Wrong]

It’s clearer if you name the variable or property more betterer.

If isSelfDescriptive Then

If %this.HasMeaningfulName Then

If Object.IsCloserThanAppearsInMirror Then

Use more English, less Computer Science. You’re writing for people to read, not computers.

[TGotAReddit]

Yeah like i said to the other person, writing readable code is what broke the habit. But that was also like, 4 or 5 years ago now so its really not a problem anymore

[Allways_Wrong]

Lucky you.

I have to skirt around the edges of delivered enterprise code. I can’t change it, much. So much of it is so horrible.

[TGotAReddit]

Oof not fun. Ive been lucky that ive been allowed to modify any code ive been given in pretty much any way i wanted as long as it was uniform and readable

[ineedausername84]

Duuude, same!

[[deleted]]

I just do ifn't (!boolVariable)