What a load of crap!
Irrespective of langauage, it comes down to your attitude.
Bad coders with bad practices and a bad attitude, create bad code.
Good coders, conscienous coders write good, fault tolerant code.
I know people who think exception handling is something the user should do via emails when they simply spit out a failure message from a piece of code! I hate the idea that a process I write will fail so I probably spend an inordinate amount of time writing handlers, backup and correction routines that will try everything possible before giving up and apologising to the operator/user that process X has failed.
The reason is that when something fails there's usually about 2 days of blame apportioning emails flying back and forth between people trying to pass the buck, I don't have time for that nonsense. So if I can do everything in my power to avoid all that, people waste less company time and money arguing and more time doing something else, even if it's less productive at least it's not near me or my processes or code.