|
Especially when you have crazy methods and flags in third-party-libraries, like "useNoVad" ... which mirror the meaning of the bool, because "true" means "no, don't use it".
If you find yourself then in constructs that combine those with && and || and, to spice it up with a !, you see a line like
if (!useNoVad || (useNoVad && !otherThingsEnabled)) ... and THEN you have a dev that doesn't like that negative version of useNoVad, and he creates a bool noVadActive, but MEANS vadActive because he assigns noVadActive = !useNoVad...
if people start to invert bool over and over again it gets crazy sometimes
|
|
|
|
|
oh nooo
that's !true
|
|
|
|
|
... is assuming it works and not testing, which usually results in a single line change to get it working.
Strangely most of my fixes are one liners, da-dum.
|
|
|
|
|
Missing option "Object reference is not set to an instance of object"
Three cheers for this error
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
Covered by "null reference error"?
|
|
|
|
|
Yes...
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
I like the fact that you can choose more than one.
|
|
|
|