Brilliant and hard work!

why

I think this is good. I think I had a similar thought process of solving this but just had it in a single function. My function was doing too much but still segmenting it would require data talking between the two and I thought that would start to get messy. I probably should have done this to segment the code while having the shared data.

mayakovsky style

Thx for OOP example, but it hard to understand it at first time.

this is so ugly . stop using oop for everything , it should be a tool ,not a fetish

Production kata solving

Interesting

This code is well organise.

this is what I probably would've done

@Haksell I guess it depends upon your background but for me yes, it's easier to read 50 simple lines than 4 very intricated ones. The same way that it is easier to read the Wikipedia page about Schrodinger equation than to understand such equation as a first approach.

Probably because he comes from Java where you're used to overengineer everything