|
Alan Campin wrote:
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.
Well, that has nothing to do with a code review ... that's just dumb people being refusing to learn. A statement like "it doesn't pass code review" means nothing ... WHY doesn't it pass code review? A review without feedback is just wasting time. I often review code ... approve the change, but put a bunch of notes on the change report (version comparison along with a copy of the defect issue) indicating different techniques that could be used, etc. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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
