|
I think code reviews are an excellent thing but the problem I have run into every shop I have worked in is that programmers end up using it as a method to make sure nothing new gets introduced. "By god, if it worked in 1985, it works and there is no reason to change" argument and the "Dumb and Dumber" argument. We can't use anything in programming that the dumbest programmer in the shop can't understand. For example, I introduced user spaces with SQL to increase the performance in a company I worked out. Worked great and easy to do but all the other programmers where having a fit. "I never done that" and so next I hear is "oh, it doesn't pass review" when the real problem is nobody wants to learn anything new. Code review becomes a way to make sure that nothing changes. Really gets old after awhile.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
