Most of the article is good, but this is weak: > If some code is throwing an error, you could just wrap it in a try..catch statement and suppress the error. No

Most of the article is good, but this is weak: > If some code is throwing an error, you could just wrap it in a try..catch statement and suppress the error. No error, no problem. Right? Sorry, for me, making the problem invisible isn't the same as fixing it. "Swallowing" an error can easily lead to other unexpected side-effects. I don't want to have to deal with them at a point in the future. I actually did work with someone else who did this sort of thing, however it is certainly not the normal in my experience, not for anyone who takes any pride in their work. Including this one really devalues the "it took so long because I'm so professional" message IMO.