It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
var hasGoodPoint = true;
var isMyConvention = true;
Also, I prefer not to pass booleans to (typically multi-argument) functions unless they are obviously expecting true or false (ie. property methods), so typically "can" or similar named functions:
This is okay:
canPost(true);
But this is not so good:
someMethod("Thing", true);
Some languages have named arguments, so in that case it'd be better to say:
someMethod("Thing", canDelegate=true);
Alternatively use enums:
someMethod("Thing", Delegation::Allowed);
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hungarian notation is dead and good riddance to it, but formulating boolean names as
isXorhasXdoes a lot for clarity.Also, I prefer not to pass booleans to (typically multi-argument) functions unless they are obviously expecting true or false (ie. property methods), so typically "can" or similar named functions:
This is okay:
But this is not so good:
Some languages have named arguments, so in that case it'd be better to say:
Alternatively use enums: