thanks for the feedback. We did lots of this kind in uni as exam, and someimes i see my fellow devs struggle with debugging, they don't always know where the code will next step. I expect this kind of kata to help with that, and a bug-fixing kata might not neccessary give that. Honestly these are some POC, while next versions might help navigating various cases like continue in for loop, or inheritance execution order, overridden functions, etc. :)
But I'll be sure to complete some bug-fixing kata before continuing.

fair point, gonna update :)

Hi,

On one end, you're talking about outputs, but on the other end, you're asking for stuff logged to the console, which are not the outputs of the functions (they all return undefined.

Cheers

While I do like the concept of 'code comprehension' katas, I don't really think the format you have is going to work.

You might want to try make it into a 'bug-fixing' kata? Those have been done, but you could focus on bugs where it is important to understand what the function does, and what it returns, to fix the bugs. Normally a bug fixing kata has a single function, but you could provide a whole series of functions (sort of like this) if you wanted.

26 could be calced from codeA and codeZ