Anchors don't float. On the other hand, that's a poor analogy, because anchors are useful for something.
The HDD industry was already over consolidated.
Really, Really? The previous margins were tiny; the current margins are thin. I like low prices, too, but I also like companies that produce quality products to stay in business...
You're clearly not writing software for a living...
There are a few things more important than security: time to delivery and budget.
Did you say that during your interview? Try doing things "right" the first time, like *always* using prepared statements. I have found that I can write code the "right" way just as fast as I can write "dirty" code, and I don't waste time debugging and refactoring. Not to mention that I never have to worry about an SQL injection attack. I'm shocked at how prevalent such attacks are, given that they are so easy to stop.
My opinion is you're a stubborn idiot.
My opinion is that a person's judgment usually reflects more on themselves than on the person they judge. Back to the original post, it seems a bit silly to me. I've spent countless hours figuring out why some journeyman programmer wrote code they way they did with no benefit from comments. At the same time, I've wanted to remove all the comments from code because they were verbose but contained little real information. Both are equally bad practices; why debate about which is worse, or use one bad practice as a counterpoint support to another bad practice?
Bottom line is, *I* have found well-written code, with brief but meaningful comments, the easiest to work on. And I don't recall meeting a person who advocates code with no comments who struck me as a solid programmer.
An adequate bootstrap is a contradiction in terms.