First off, this meta post discussing 'debug my code' criteria covers why these types of questions are frequently considered off-topic &/or of low value. Basically, this is the system doing what it was meant to do. While there is almost certainly value to you in having your code debugged, the value to others is not very high relative to the other sorts of questions that are on-topic & favorably received.
Also, as pointed out by others, feedback on a specific working piece of code with regards to best practices, performance & correctness is very on-topic for Code Review. If that's what you want, that's where to post.
Beyond that, if you want a specific answer, ask a specific question. At a minimum, identify the expected behavior & the observed behavior for your code.
You wouldn't take the response "you didn't code it right" to be a very useful answer - it might be technically correct, but it doesn't show much effort & it doesn't contribute much to fixing the problem. The same is true of "what's wrong with my code?" - it's a question, but without some additional work, it's not a particularly useful question, either to those who might answer it or to those searching for answers. If you can't at least identify the expected & observed behavior, we really don't have much to go on.
Better yet, try to provide a minimal, complete, and verifiable example (MCVE) of your problem. It's a good skill to cultivate & sometimes the very process of making a MCVE will result in identifying and correcting the problem yourself.