he missed out on the programmer as the biggest problem:
a) underestimates the work.
b) overestimates personal abilities.
c) lacks the exerience to prevent a+b.

..either you take care if his coding and help him or her, or you leave for a new job...
I personally chose to help and correct the code of a co-worker for almost five years, only to get more and more frustrated. In the end, it was too much to take, as he didn't even care. He had given up learning and caring for his job, but he tried to push me around because he was older... of cause this depends more on personalities than coding, but my advice is to tread carefully. At the end, being right can be patronising and putting the co-worker on the defensive. After all, he might be aware of his short-comings and start playing the politics card... and then it becomes ugly!

I've found, that promising sweets, say a tiny pack of gummibears, for any new error, that has not been seen before motivated everyone.
Simply ask them to make screenshots to prove that it is a new error and you are of.

Think about it. Finding Bugs this way makes fun and is totally worth the packet of sweets.
This really works!