It might be easier to read when you have pages of code with many different functions.

Sometimes the descriptions can be overworded or underworded. Information theory and the beginning of words is a very cool subject to research if you can. If you see kata with bad descriptions, you can leave a suggestion in the discussion section to help improve the understanding of the goal for other Code Warriors.

made me realize this kata is overworded

Hehe calculus programming ^-^

Nice
i wanted to try something like this but couldn't. Thanks for the help

That's the thing, they aren't. It's a culture thing :D

People just upvote one-liners as best practice for the sole purpose that it compacts more code into a smaller space and is thus seen as minimalist or cool.

Of course, sometimes (such as for list comprehensions or for cases where it's easier to use a built-in function) one-liners are actually best practice, but half the time, it's more likely to be someone using some esoteric, relatively niche and/or inefficient code in a one-liner.

But it's been 11 months so you probably know by now.

So that's what that meant.. Nice one! :)

The deck is preloaded.

I get how this should work in priniciple, but how is it passing any tests with only this portion of code? Where is it getting the "deck" from ?

i had the same answer, but split into two lines 'cause of the indent. It's a great habit to get used to, especially for larger and more complex projects, so it's easier to read.

Python: should not use sum as variable name.

one liners can be clever, but not best practice most of the time (I agree with you)

one line fantastic

I fully agree with you. It should not be. This is not so clear especially for the beginners like me.