Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
the || to me is for aesthetically pleasing so I certainly agree this ranks higher than &&
Don't know why this is so far below the && solution.
But I am happy I finally got one of the top answers on my Kata.
Very concise with the ternary. Good work!
There are people who can't do math, so...
Why isn't this solution best practice? It seems so simple and straight forward.
Thank you @St3f4n i understand it now i'm a beginner in JS thats why it seems weird for me.
It's shorthand for Number(), so it's just a simple converting to a number.
can somebody explain to me why in the code there is the plus sign in the beggining of the code in my code i used parseFloat but this plus in the beggining i didnt understand .
666
I see, then these websites are wrong, when they state that the let keyword is part of the ES6 and newer:
https://medium.freecodecamp.com/5-javascript-bad-parts-that-are-fixed-in-es6-c7c45d44fd81#.xuzvyk491
https://strongloop.com/strongblog/es6-variable-declarations/
https://davidwalsh.name/for-and-against-let
Sorry, just a little confused.
no, this is not ES6 dependent
This will only work for ES6, right?
Additionally, I didn't even think about putting a conditional test as the property value in an object! Very succinct and novel.
This is great! I used your code if you don't mind in my blog and tried to explain how it works.
This comment is hidden because it contains spoiler information about the solution
"Hundreds of rows" and "extra columns"? That's adorable.
My friend, my current job right now is writing code to generate exports on top of a data warehouse. Tens of thousands of rows are not uncommon. One export has over 300 columns. We weren't satisfied with any of the available data structures (there's extensive post-processing of the data), so we wrote our own. What we did not say is, "Well, screw it, let's just use Records. It's dirt slow and frustrating to work with, but at least we don't have millions of rows. Until next year, anyway."
Loading more items...