Since the mid-80's, when I was finally forced to deal with 'C' on an ongoing basis, I found that most 'C'-coded projects not only lacked quality-control, but also lacked quality. Largely, this was paired with a complete lack of documentation, which is often the case with sloppy work.

I associate this with the stereotypical image of the long-haired (it was unpopular with conservatives), jeans-wearing, Pepsi-drinking software type, saying, "... no-problem ... we'll just <insert ad-hoc fix here> and it's done" ... no requirements analysis, no timing analysis, nothing of any value to subsequent maintainers, and probably no consideration of possible side-effects.

While I've not taken to wearing my hair long, I do wear jeans, and I dislike neckties ... a symbol of that "appearance over substance" culture that I detest. Nonetheless, I see software types taking a sloppy approach, starting to code well before they've done any of the normally required analysis and design work. I believe that much of this results from the fact that 'C' compilers compile code that doesn't run, which gives programmers the false impression they're close to a reasonable solution.

RE