"And I don't like this kind of help. Mainly because it has several problems.
First of all it is not clear that it is visible to the author what
the actual problem is and what solved it so that the bug doesn't occur a
second time or at least can be identified. Also keep in mind that the
exercises are rather short so in the end the codes will all look pretty
similar and an "I almost got it" might not always be correct. Also the question "typo or lack of understanding" is an individual one. The second thing is it is not save that it is really a solution and free of bugs. That is of course a risk every comment has but for just code comments it might be worse. Third, all the exercises
should be possible if you stick to the instruction both technically and
from understanding. And if this is not the case it is better to point
that out than give advices on how to "cheat" on the exercise. And as it is about learning your basically cheating on yourself because this may lead to a lack of understanding of the basic concepts.
There might even be more reasons but I guess these are enough for
now. I'd rather recommend using code snippets showing the problem and
giving hints about the underlying concept. Or at least mark the problems
in your solution.
Also there is no reason for posting a solution if there is already a solution
in this post, this just makes the topic unnecessarily long and
confusing. At this point I'd like to cut this to not make the post any
A quote I wrote elsewhere. So I'd rather say do not post solution buts hints and if you do at least give some information with it so that one can see where the problem is and how to solve it.