I like the method of challenging the devs' assumptions and approaches and let them figure out where the gaps are by themselves rather than feeding them the answer. This a very common thing we do at Amazon where we try to help people grow organically by following a more socratic method. You can still give the dev full ownership and let them break stuff as long as the impact is not catastrophic (eg: legal issue or affects customer money), and a correction of errors/postmortem is highly recommended in the case of mistakes so that they learn what the root cause was and how it can be prevented in the future.
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 like the method of challenging the devs' assumptions and approaches and let them figure out where the gaps are by themselves rather than feeding them the answer. This a very common thing we do at Amazon where we try to help people grow organically by following a more socratic method. You can still give the dev full ownership and let them break stuff as long as the impact is not catastrophic (eg: legal issue or affects customer money), and a correction of errors/postmortem is highly recommended in the case of mistakes so that they learn what the root cause was and how it can be prevented in the future.