Ad
  • Default User Avatar
  • Custom User Avatar

    Thanks for your kind feed, albeit I fear I will disappoint you sooner or later, as I try to diversify my interest (and my offer to my trainees) in katas, ranging from very basic to more advanced katas, so not to easy to stay that palatable.

    Just be sure to tell me what I do wrong, anyway :)

  • Custom User Avatar

    Another 'sweet' ;) kata from Mr Sorbi. Be careful, you're in danger of becoming my go-to kataist.

  • Custom User Avatar

    Thanks for your kind feed too, Hadron :)

  • Custom User Avatar

    Very good kata. Nice introduction to this level for me. Simple instructions, but still some hard work. Will look out for your others.

  • Custom User Avatar

    This looks like a case of the instructions not being followed to the letter.

    'If one or more of the opponents pieces are sandwiched by the piece just played and another of the current player's colour...'

    Emphasis on 'just played'.

    In the play sequence that both MariusAFT and jkranking refer to, neither of the adjacent pieces are 'just played'.

    Instead, white has cleverly inserted his piece between two of his opponents previously played pieces, rendering his piece safe.

    It caught me out too. If I'm right about the reason then this specific error message might need revising as it's misleading.
    Good kata, however.

  • Custom User Avatar

    It was a mistake on my part. Well spotted, thanks.

  • Custom User Avatar

    Am I misreading your explanation...or in your examples have you mistakenly marked the fourth group of characters — 01010110 — as an error when actually it is not?

  • Default User Avatar

    Yup, I think this kata's whole point was code efficiency.

  • Custom User Avatar

    Passed all tests, but CW kept timing out when I tried to submit. Took me longer to refactor my code than it did to write it in the first place. Shaved off a few seconds here and there, cursing you at every turn...until I managed to sneak it under the wire and realised that it was a good lesson in code efficiency. So thanks for that...and apologies for the bad language albeit unheard.