• Sign Up
    Time to claim your honor
  • Training
  • Practice
    Complete challenging Kata to earn honor and ranks. Re-train to hone technique
  • Freestyle Sparring
    Take turns remixing and refactoring others code through Kumite
  • Community
  • Leaderboards
    Achieve honor and move up the global leaderboards
  • Chat
    Join our Discord server and chat with your fellow code warriors
  • Discussions
    View our Github Discussions board to discuss general Codewars topics
  • About
  • Docs
    Learn about all of the different aspects of Codewars
  • Blog
    Read the latest news from Codewars and the community
  • Log In
  • Sign Up
Fluffy Avatar
Name:Anthony
Clan:Unknown
Skills:ruby, html/css, javascript
Member Since:Mar 2013
Last Seen:Feb 2019
Profiles:
Following:0
Followers:0
Allies:0
View Profile Badges
  • Stats
  • Kata
  • Collections
  • Kumite
  • Social
  • Discourse
  • Conversations (18)
  • Replies
  • Authored
  • Needs Resolution
  • Custom User Avatar
    • mdandre
    • commented on "Statistics Algorithm - Calculate Mean" kata
    • 3 years ago

    tests are wrong: they look for an add function with diff params

  • Custom User Avatar
    • willfowls
    • created an issue for "Statistics Algorithm - Calculate Mean" kata
    • 4 years ago

    description says input is always an array not including non integer or non float elements. test case passes just a string

  • Custom User Avatar
    • WestwardLand968
    • created a suggestion for "Statistics Algorithm - Calculate Mean" kata
    • 5 years ago

    This comment is hidden because it contains spoiler information about the solution

  • Custom User Avatar
    • WestwardLand968
    • created an issue for "Statistics Algorithm - Calculate Mean" kata
    • 5 years ago

    Use Test.assert_equals

  • Custom User Avatar
    • suic
    • commented on "Statistics Algorithm - Calculate Mean" kata
    • 7 years ago

    The author has been inactive since January 2014. As I see, many of old Ruby katas have have poor quality according to today's standards. I'm not sure if it makes more sense to fix or to retire them. (Btw. in Python this would be max 8kyu :))

  • Custom User Avatar
    • gopheratl
    • commented on "Statistics Algorithm - Calculate Sample Space" kata
    • 7 years ago

    @max30272 it really should. The description explicitly hands you the math to peform, so the kata boils down to two very basic "how do I X in ruby?" questions, and if your solution is more than 1 line you're doing something very wrong.

  • Custom User Avatar
    • max30272
    • commented on "Statistics Algorithm - Calculate Sample Space" kata
    • 7 years ago

    It should be 8 kyu. :(

  • Custom User Avatar
    • anter69
    • commented on "Statistics Algorithm - Calculate Sample Space" kata
    • 7 years ago

    Added various other dice to tests

  • Custom User Avatar
    • anter69
    • resolved a suggestion on "Statistics Algorithm - Calculate Sample Space" kata
    • 7 years ago

    Updated description and added sample and random tests

  • Custom User Avatar
    • anter69
    • commented on "Statistics Algorithm - Calculate Sample Space" kata
    • 7 years ago

    Re-ranked to 7 kyu

  • Custom User Avatar
    • anter69
    • created an issue for "Statistics Algorithm - Calculate Mean" kata
    • 7 years ago
    • description is contradictory with tests: "Inputs are always populated (non-empty) arrays" -- however, empty arrays are tested
    • description poorly formatted
    • no sample tests
    • no random tests
    • overrated -- this is max 7 kyu
  • Custom User Avatar
    • Voile
    • resolved an issue on "Statistics Algorithm - Calculate Sample Space" kata
    • 8 years ago

    Fixed

  • Custom User Avatar
    • ice1000
    • commented on "Statistics Algorithm - Calculate Sample Space" kata
    • 8 years ago

    Too easy to be a 6kyu

  • Custom User Avatar
    • bouchert
    • created a suggestion for "Statistics Algorithm - Calculate Sample Space" kata
    • 8 years ago

    The description is poorly formatted, introduces the problem in a somewhat awkward order (e.g., listing expected output before explaining what the input is), devotes way too much space to irrelevantly listing permutations which might mislead someone into thinking they're expected to return those, and there are no example tests to clarify what is expected.

    At the very least, that long line (without breaks, making it even less readable) that reads:

    all_possible_outcomes_of_multiple_trials(coin, 2) should == 4 all_possible_outcomes_of_multiple_trials(coin, 3) should == 8 all_possible_outcomes_of_multiple_trials(dice, 1) should == 6 all_possible_outcomes_of_multiple_trials(dice, 2) should == 36

    should have been turned into example test cases and placed in the test section.

  • Custom User Avatar
    • bkaes
    • created an issue for "Statistics Algorithm - Calculate Sample Space" kata
    • 10 years ago

    expect shouldn't be used on values that can be tested with equality. Use Test.assert_equals instead.

  • Loading more items...
  • © 2025 Codewars
  • About
  • API
  • Blog
  • Privacy
  • Terms
  • Code of Conduct
  • Contact

Confirm

  • Cancel
  • Confirm

Collect: undefined

Loading collection data...