In this video, we'll talk about other things you need to keep your mind upon, aside from just solving problems. Since you're probably just begging your way, in competitive programming, if you read this course then, it's completely fine for you to be stuck on something like a hard idea of solution or some non-trivial back implementation which you couldn't find by yourself. And if that happens, it's a good choice to ask the community for help. There are a lot of people which would like to help you if you ask right. So, where to ask questions? First, there are forums here in this course where we encourage you to get help. But there are also forums on different popular resources committed to a condition for competitive programming. And we'll discuss those resources later in this lesson. But when asking questions, you should expect completion rules, for example it's cheating if you want to get help on a problem from an ongoing contest. And you should not also discuss like examination questions and something like that, but everything else is fine if you for example, the contest has ended then you have all the rights to ask something about the problem. So, if you decided to ask people about something, it's very important to do it well so people would like to answer you. First of all, you should put a title, summarize what you're asking about because it's the first thing that the people will see. You should also format your question and code in it well so the people could easily understand what you've written. And you're probably should insert just enough codes so the problem will be reproducible because if you just put 200 lines of code and ask where is the bug, then no one will be able to help you. In fact, on competitions, there's also a chance to get help but on that particular form. If you don't understand something in the problem statement, you could ask the jury for clarification. That is, you could submit in a special place a question which assumes answer Yes or No, and is about the statements. Most probably, the answer to it is already written and you just didn't get it. But if it happens that something is not clear in the statements and that the jury could fix it by answering your question. Of course, the jury will not tell you anything about your solution or other people's solutions, only about the problem statement because helping you get the right solution is not their task, you must do it yourself, that's the competition rules. But if you're seriously stuck on the problem, you might just wait until the end of the contest and then ask the community about your problems. Another important part that people often miss is establishing workflow, meaning that, as time means everything on the contest, you may probably want to do routine things faster like creating projects, testing debugging and so on. So first of all, it's good to get to know your either IDE or text editor well so you could fast create projects, open your files, debug and so on. It also is good enough to have a template code so you don't just start writing every solution from the scratch but from some already written code like popular includes or some functions you need or something else. It's also a good thing to find a way to manage your backups of your code and tests because it's often needed to, well, you could write something incorrectly and then delete it, and then want to return it back. So backups may be helpful and there are different ways to do it. For example, sync in folder so, version system or just manual copying, you could choose any one of them but you should not spend many time on it.