Earlier quoted context omitted.
This is exactly the kind of thing I'm talking about though. I believe a lot of this bad advice stems from thie belief that "other people write bad software." When you run into bugs day in and out, it's easy to reinforce this belief. Afterall, how can someone who claims to have all this experience and knowledge make such an obvious mistake? They're paid a salary and millions of people trust their software! I could do…
I empathize with what you are saying, but I don't agree. I think it's crucial to recognize the difference between what I'm talking about, and what happens when people with experience make mistakes. Environment matters, tremendously. If you're an amateur hack, selling your 3rd rate skills to customers who don't know any better, and you're lack of capability is hurting people because your software is being exploited, t…
I'm not even talking about doing something as silly as charging a client money for something you barely know how to do. That's just deceptive business practice and people should be lambasted for it. Misrepresenting your capabilities is reprehensible.
What I'm talking about and what I think the OP was talking about is the negative attitude we have towards our fellow geeks. We discourage people from learning or trying their own ideas out. I think that's pretty sad. Even if they are re-inventing the wheel; let them try, man. Maybe they will end up with a better wheel. Or a special kind of wheel. You never know if you just tell them that it's already been done and they couldn't possibly build a better one anyway.
So while I agree that some sort of safeguard against malicious business practices would be useful to the industry as a whole, I don't think it has anything to do with supporting a negative attitude towards our fellow geeks. Everyone has started somewhere and it's better to foster and encourage learning and experimentation than to institutionalize the practice of programming.