[mafribe]

It's useful to get human feedback on one's code, but human attention is scarce, and human judgement is influenced by many non-technical factors (e.g. mood, politeness or hostility) that do not derive directly from code quality.

For these reasons, I recommend complementing internet-based code review by measurement: Use (automated) testing in multiple forms, unit, integration, randomised. Count the number of bugs you encounter. Classify the bugs you find, track how the numbers and classes of bugs in your code evolve over time. Compare those statistics with other coders. This not only gives you ideas about your relative coding ability, but will also reveal areas where you could try and improve your abilites.

[nikant]

I wanted to get some feedback on my code design and structure. I think that is difficult to get via automated code review.

[mafribe]

That's not what your question asks for.

Anyway, in my experience, the ability to test with ease is one dimenision of design quality.

[RussianCow]

How is that not what was asked? The phrasing of the question makes it immediately obvious, at least to me, that the OP was looking for a design critique. (Unless of course the question was edited since you wrote your initial comment.)

[enraged_camel]

>>That's not what your question asks for.

Maybe you didn't read it, but the question clearly and explicitly says: "Be brutal and honest about what you think of my code structure and style."