From an emotional point of view, the life of a developer is like a rollercoaster. Days of anxiety from performance expectations and low self-esteem when no coding solution seems to be easily found to days of pride and happiness when you can finally find a solution.
Recognizing this "rollercoaster pattern" has helped me many times in my professional career. If I do not get easily a concept or do not figure a solution out at first, I do not beat myself down, because I know that it "just" means I have to do some more effort, that I need a bit more time - for more research, for more study. Or that I need to decompose the problem in smaller more meaningful problems/tiny baby steps, that I can solve. Learning, and particularly learning to code, is never easy, it comes with a mental cost. Just like gym workouts, some are tougher than others and require more willingness to "suffer", to obtain a change. But when you realize that you changed the way you wanted, oh boy! That moment is pure joy.
If I am "too deep into the spiral of hopelessness" because of coding, I would code anyway, as a response. In the best way I can, even if my best coding contains still a lot of mistakes.
I would need to qualify "code anyway", though: I mean, I would keep on coding, but with the reserve of not getting mentally exhausted. If you are a sport type, then exercising can help a lot to avoid mental exhaustion. Dancing is particularly cheerful and regenerating for me, for instance. But I get a great mental relief from drawing, too or playing piano. Arts in general can offer great mental helps - both if you practice them actively or if you just "consume" them (by going to an art museum instead of drawing or listening to music, instead of playing it, for instance).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
From an emotional point of view, the life of a developer is like a rollercoaster. Days of anxiety from performance expectations and low self-esteem when no coding solution seems to be easily found to days of pride and happiness when you can finally find a solution.
Recognizing this "rollercoaster pattern" has helped me many times in my professional career. If I do not get easily a concept or do not figure a solution out at first, I do not beat myself down, because I know that it "just" means I have to do some more effort, that I need a bit more time - for more research, for more study. Or that I need to decompose the problem in smaller more meaningful problems/tiny baby steps, that I can solve. Learning, and particularly learning to code, is never easy, it comes with a mental cost. Just like gym workouts, some are tougher than others and require more willingness to "suffer", to obtain a change. But when you realize that you changed the way you wanted, oh boy! That moment is pure joy.
If I am "too deep into the spiral of hopelessness" because of coding, I would code anyway, as a response. In the best way I can, even if my best coding contains still a lot of mistakes.
I would need to qualify "code anyway", though: I mean, I would keep on coding, but with the reserve of not getting mentally exhausted. If you are a sport type, then exercising can help a lot to avoid mental exhaustion. Dancing is particularly cheerful and regenerating for me, for instance. But I get a great mental relief from drawing, too or playing piano. Arts in general can offer great mental helps - both if you practice them actively or if you just "consume" them (by going to an art museum instead of drawing or listening to music, instead of playing it, for instance).