I write this from the perspective of having been the junior and received the mentoring and guidance from an experienced colleague.
Be gentle, work with them, allow them to explore the code-base and to experiment.
Take things slowly, do pair programming, discuss what is needed to be achieved and how to do it; this is even better if options can be discussed with their individual pros and cons.
The first few months are likely to be tough, though don't choose massive huge features, start with something useful but small, maybe even a bug to investigate; though that could go the other way of being painful.
If you do pair, don't do so in a way that you would work by your self, you have to go slowly and have a really open dialogue. Those thoughts that zip through your head have to be slowed down and verbalised; your newbie will learn a lot of the process of programming as much as the technical stuff.
Admit when you don't know something and that it's something that can be worked out later together or individually.
Don't assume their skill level; it might be their first pro job, but they may have been writing for a while...
Whilst all this sounds like you're holding their hand, give them the space to do their own tasks, then do the code review together to be able to discuss the change; requirement specs, solution, implementation, etc...
You mentoring \ training them makes you a better pro.
I hope these help.
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.
I write this from the perspective of having been the junior and received the mentoring and guidance from an experienced colleague.
Be gentle, work with them, allow them to explore the code-base and to experiment.
Take things slowly, do pair programming, discuss what is needed to be achieved and how to do it; this is even better if options can be discussed with their individual pros and cons.
The first few months are likely to be tough, though don't choose massive huge features, start with something useful but small, maybe even a bug to investigate; though that could go the other way of being painful.
If you do pair, don't do so in a way that you would work by your self, you have to go slowly and have a really open dialogue. Those thoughts that zip through your head have to be slowed down and verbalised; your newbie will learn a lot of the process of programming as much as the technical stuff.
Admit when you don't know something and that it's something that can be worked out later together or individually.
Don't assume their skill level; it might be their first pro job, but they may have been writing for a while...
Whilst all this sounds like you're holding their hand, give them the space to do their own tasks, then do the code review together to be able to discuss the change; requirement specs, solution, implementation, etc...
You mentoring \ training them makes you a better pro.
I hope these help.