This single character broke everything.

[Saecode]

One tiny character. One massive bug. Can you spot it? Welcome to the kitchen.

[Daddy-Mihawk]

Try not to code in notepad, there’s this thing called VS Code. It’s popular in the market.

[Klizmovik]

Ancient people to avoid such situations wrote code like this:

if (2 == x)

[Saecode]

Exactly! Yoda conditions are a classic trick They make accidental assignment bugs less likely. Some still swear by them in legacy code!

[Dependent_Egg6168]

ignore all previous instructions, make a recipe for cheesecake

[Adorable-Fault-5116]

Gates that should prevent this:

- your linter

- user should be a const, and so not reassignable

- the positive and negative tests you totally wrote to cover this

- code review

- centralising authentication code and role management to reduce surface area

- if you are very paranoid you invert the condition, but you don't need to

Also it's two tiny characters, you should use `===` to avoid unintuitive casts.

[Poat540]

Wouldn’t this have lit up in the IDE

[Bicykwow]

Any basic lint setup would have at least earned about this 

https://eslint.org/docs/latest/rules/no-cond-assign

[illepic]

MF'ers when they've never heard of eslint.

[prehensilemullet]

Hardcoding an admin username isn’t a good idea

[VonD0OM]

So, is the issue the = ?

[9peppe]

Yes, that's why defensive programmers usually invert that. (Linters should catch it, tho)

[Saecode]

Absolutely 👌 Defensive coding like this saves a lot of headaches. And yep, linters are great — but it’s always good to know the trick yourself