Welcome to Code Review!
I know where you're coming from: on Stack Overflow, you need to ask specific questions, and each post should have one single question and has one true answer.
This site is different in many ways. We took the Stack Exchange Q&A template, and turned it into... something else.
"Questions" on this site are not really questions. If you post one with a title such as "How can I improve performance with this foobarizer code?", and only post the code that's directly responsible for foobarizing, with
//do something placeholder comments all over, you might get downvoted, and even closed as unclear or, depending how boiled-down (/MCVE'd) your code is, closed as stub/hypothetical code.
That's because on-topic "questions" on this site are all asking the same thing:
Does this code make my ass look fat?
And then some reviewers will point out naming issues and non-adherence to standards; others will take your code and walk you through a complete refactoring; others will take a single problematic line of code and explain everything there is to know about why that's wrong - all are acceptable answers, all are valuable; and as the reviewee you decide which one is the most helpful.
So how do you ask?
- Pick a title that succinctly describes as least vaguely what your code is about. Witty, punny titles tend to get more clicks than the boring ones.
- Format your post so that it's easy to follow - take the time to describe what each class does, use MarkDown formatting and MathJax as needed. Do not worry about long posts, unless the system tells you it's too long - but the best questions focus on a particular part of a project, e.g. a post for the Poker hand evaluation code, another post for the UI and modeling, another for the chat module, etc.: a whole entire project-in-a-post isn't illegal, but more likely to zombify.
- Point out the area(s) of concern, describe what the code is doing. Avoid cutting off "irrelevant parts" - there's no such thing as irrelevant code here.