I propose to retire this kata.

Coding is all about problem solving which this is ;).

I don't know why you've been downvoted. You're right.

Imgur seems reliable. Just avoid Tinypic and Photobucket.

Hi! ( Been away for a couple of days. )

Retirement is permanent. But you can make another kata! This one's biggest problem was it lacked originality though, so reposting this same one is probably not going to give better results. Still, learn from the comments on this one. The big things these days are random tests and an idea that hasn't been done to death. The latter is difficult; there's 8000+ kata already, so a lot of things have been done ( some of them, to death ). The former is rather less difficult, but it's not optional or "can do later".

Random testing is not just for preventing hardcoded solutions; it's also great for finding edge cases. Your own solution may have more edge cases than you thought, and solvers' may have edge cases you never even considered. For that reason, keep your random generators very general and really random; for testing specific cases that may be edgey, have fixed tests. If random testing finds any edge cases while creating your kata, add fixed tests for it ( people will sometimes tweak their random generator to generate specific tests. that's not what random testing is for [ and it isn't random :] ). If I solve a kata and random testing ( possibly only sometimes ) finds a bug in my solution; I will often comment so the test can be added as a fixed one. ( But most people won't. )

A fork is exactly what you describe; it can be used to iterate on your own or somebody else's solution. ( It's also a way to look at Preloaded code in a kata. :) It's not really an edit, and it's not even necessarily a solution because you can also edit the tests ( I've used it to propose better tests without changing the actual solution, and I've used it to showcase a different solution with [ performance-wise ] lighter testing ).

A nice and understandable one. Thank you.

Thank you. As a self-taught programmer I think I really need this, so your edits are highly appreciated. There is some difference between solving (that is, actually using) and creating tasks. There is obviously a lot to be learned by doing the latter.

What can I do with the code you have provided? Can I somehow take it back into the kata, and republish it; or is 'Retired' a permanent condition which means it is unavailable for any improvement and is trashed once and for all?

I really lack knowledge about collaborative programming. That is, I know how to write something (some small thing) on my own and push or pull things to/from github, but not together with other folks. So even what a 'fork' means is not completely clear to me. I sort of understand that it means changing somebody else's code and publishing with a link to the original but that might not be true either.

Hello,
I got it. I will try to improve this. I haven't written a kata before, so I will try and make use of everything you experienced guys write here. Thanks!

Thank you, I will try to fix it. It's my first kata.

Would have benefited from blocked words of different lengths. That would have made the task ( ever so slightly ) more interesting.

There is this one test where the blocked word is not the entire word. Behaviour around that is completely unspecified. Most interesting option would probably be to require that only complete words are blocked. But specify such things, escpecially when one of the blocked words already is a plural!

Hi,

• well, it has been done already... :/
• it would need random tests
• you don't talk about the behavior with plurals in the description
• missing a lot of edge cases with false (?) matches: caller, codewars, ... => the behavior is undescribed: should they match or not (I feel like they shouldn't)

cheers

The image is unavailable, so there is no example now.
First I was amazed at the input image. But five minutes later I understood it was not the actual example but the 'unavailable' plug.

Say console.log(peopleInLine) and you will know at least what you get at the input, so it will help you sort it out.

I think the random tests should be done again, but for now, they should work.

Redone.

Found several edge cases by way of random testing; these have been added as more fixed tests.

As mentioned above, I've done describe and it headers to unmuddy the waters.