If you don't like to code then don't push it, try something else.

Don't miss AtCoder Beginner Contests.

And if you wish, take a short break from codeforces contests.

And, when reading the editorial, don't just read it and solve the problem. But also, try to change your thinking style by checking what you had missed in that problem but someone who solved didn't.

If you are thinking Codeforces as a 'tutorial' site, you are in the wrong place. That's why you are getting downvotes. However if your first coder's website is Codeforces.. I understand that you would be unfamiliar with these Algorithms.

Next time try to google and search youtube. There are plenty of guides for who had the same worries. For example, William's Video is great.

Below is my thoughts being expert in Codeforces. Div3 A~D, and Div2 A~B is usually ad-hoc. Which means the main key is the 'observation'. Which isn't quite related with pre-knowledge. So you just need time and effort to observe ideas quickly. But for Div3 E~F and furthermore, algorithm knowledge is necessary.

I always think studying this Guide would be wonderful for anyone who think their knowledge is insufficient. Be aware that you should solve the recommended problems. The details between Theory and Reality are often different.

Starting from Codeforces?, I know it is difficult... Try solving A, B, and C from Atcoder Atcoder Beginning Contest ABC.

Feeling demotivated is normal in CP, remember that, BUT what have you done in this 3-4 months?, just solved problems? or improved your knowledge...?. 1st try everything you know on that problem, if you still don't understand, then try reading Editorial, and after reading that, if you got the general IDEA, stop reading Editorial and start implementing what you have read... REPEAT this process...

All the Best!!!

hey there, well, I don't have much to say in CP, just a newbie here, but after some years of programming I understood that solving problems should be only for enjoying.

solving problems needs a lot of time, especially at the beginning stages, and thinking of other things instead of the joy of problem solving will only bring harm

I don't say that this is absolutely the correct approach toward CP, but it's working for me (as a newbie). don't think on the time past by and no problems solved, or the people that are better than you or any other distracting stuff, just think on the problem and enjoy the full procedure.

also, not everyone can improve after three months of programming, give yourself and your brain some time to adapt to this kind of problems and algorithmic thinking.

and about reading editorials, my suggestion is to at least think on a question for a day and a half, the thinking itself is much more important than solving a problem and when you really want to go read the editorial, think of the great joy of an accepted submission that is 100% yours, this has helped me a lot to put hours of time on a question.

but again, there are more experienced people here, so you may want to listen to them rather than me. anyways, hope you high ratings :)