I liked how this kata focuses on something small but conceptually important. It’s a nice reminder that understanding how slicing works — especially thinking in terms of ranges and what to keep vs. what to remove — can lead to very clean approaches. Simple on the surface, but it encourages careful reasoning about indexes. Thanks for putting together a neat and focused exercise!

Big thanks to the kata author! 🙌
This was a clean, well-designed exercise that really highlighted
the difference between mutating an instance and returning a new one.
Loved how it encourages thinking in terms of immutability and pure functions.

Thanks for this kata! I liked how it mixes string parsing with structured data — simple yet satisfying to solve. Clean logic and a good reminder of careful data handling. 👏

No, I'm from Mars :)

Thanks for keeping this one short and clean — love how a simple formula can still be satisfying to implement. Quick conversion, no overthinking. Nice little warm-up kata!

More of a math problem than a javascript fundamentals problem.

thats what im thinking about

Thanks for this fun kata! Clean and straightforward solution. 😊

why not use burgers per footbal fields?
or better yet - muskets per moon landings?

There is only one sample test in Swift, and returning "green" will pass it, your code doesn't pass the Attempt tests, not a kata issue.

approved

Fixed for all languages, changing the last exclamation mark to a period