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.
Tests hardened, your solution now fails.
Hi,
It's in the title: "code-golf". If some ppl don't like chinese food, they just don't enter chinese restaurants, instead of entering and claiming "the food is bad, you should write on the storefront you serve chinese food!".
Do you see my point?
Cheers
That's what code reviews are for (to check for code smells and to eliminate bad code).
I joined Codewars recently. To be honest, it was the first time I learned about Golfing.
I agree it is fun and it makes you think out of box, however some people may think it is a better way even for production. As you can see Mauro-1's comment: 23-chars solutions are readable and better then ceil.
The reason why I joined Codewars was to show our new colleague a place where she could train and improve her skills. You all commenters are the top 1% of developers, however there are also people learning how to code. Perhaps it was my wrong assumption that Codewars is a good place where new developers can train their skills?
also, its fun
It's most cromulently stated quite literally in the TITLE OF THE KATA what type of code style is expected.
Any savvy individual that takes code seriously will learn pretty quick in their study that golfing is not for production.
If it is really needed, I can add one line to mention that it is a golfing kata...
If it is really needed.
Kata's are generally NOT about production code, so I'd say such a disclaimer is unnecessary and only adds noise to the description.
This comment is hidden because it contains spoiler information about the solution
If you comapre how short is your code with someone else then yes, it is fine.
However this kata is perfect example why Golfing is horrible idea if you maintain code in a team. The team usually doesn't consist of top 1% of world developers. Every average developer reading such code would need to put special effort to understand such piece of code.
23-chars solutions are readable and better then ceil.
Easy, just add random tests. Something like this:
This should clearly state that Golfing is not recommended for production coding as it makes code less readable.