• 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
hughoc Avatar
Name:Unknown
Clan:Unknown
Member Since:Jan 2020
Last Seen:Oct 2020
Profiles:
    Following:1
    Followers:1
    Allies:1
    View Profile Badges
    • Stats
    • Kata
    • Collections
    • Kumite
    • Social
    • Discourse
    • Conversations (3)
    • Replies
    • Authored
    • Needs Resolution
    • Custom User Avatar
      • A.D.Michael
      • commented on "You only need one - Beginner" java solution
      • 5 years ago

      It is not the best way to use A==B to compare strings. Although most of the time A==B can successfully check whether two strings are equivalent, sometimes something weird may happen when using A==B. The method A.equals(B) is a better choice.

    • Custom User Avatar
      • hughoc
      • commented on "You only need one - Beginner" java solution
      • 5 years ago

      I have something similar to this but I was wondering if == is adequate for string comparison.

    • Custom User Avatar
      • hughoc
      • commented on "A Needle in the Haystack" kata
      • 5 years ago

      I am getting something very similar:
      expected:<found the needle at [position ]3>
      but was:<found the needle at []3>

    • © 2025 Codewars
    • About
    • API
    • Blog
    • Privacy
    • Terms
    • Code of Conduct
    • Contact

    Confirm

    • Cancel
    • Confirm

    Collect: undefined

    Loading collection data...