Watching a tutorial.

* Uses the mouse in order to select and format code, instead of the shortcuts VS code provides

* Does multiple "bool == true"-comparisons

* Doesn't use string interpolation and makes unnecessary .toString() calls

* Adds fucking parentheses around the whole fucking expression he wants to assign
value = (expression)

* Explanations so vague, the EU wants to hire him to reform the internet

Fucking waste of time even on x2.25 speed.

  • 9
    The last point made me chuckle ๐Ÿ˜…
  • 10
    Adding parentheses around an expression is good for readability in some cases.
  • 2
    @ewpratten There are IMHO better ways to make an expression more readable. Like splitting it into several expressions or at least splitting the expression into several lines
  • 1
    @Dekatelon @ewpratten The thing is that the expression was literally just a comparison between 2 booleans, so I don't think that the parentheses make a difference๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚
  • 0
    U just made me curious, would you be so kind and share the source? :O
  • 1
    In defense of the guy. In some languages like JavaScript is good to use conditionals with arguments like myBoolean === true. Just to make sure nobody made myBoolean a number or is just defined.

    If you have myBoolean = ‘’ and you do if(myBoolean) it will return true!

    So it makes no harm to use === true in JavaScript at least.
  • 0
    @zututukulipa https://youtube.com/watch/... hope you have enough spare time for that one
  • 0
    @diegovincent However the OP says that these are "bool == true" comparisons as opposed to "bool === true" comparisons.
  • 0
    @Mathtauathogen I know but I didn’t want to assume that the language was JavaScript. In most of the languages the equality comparator is always strict as opposed to JavaScript :)
  • 0
    @diegovincent actually ''==false.
Add Comment