3 ms·
Using your code review process to hold changes ransom until they meet some lofty ever-changing team ideals, is disfunctional. "Upgrade as you go" policies leav
by a13o 3y ago
Using your code review process to hold changes ransom until they meet some lofty ever-changing team ideals, is disfunctional.
"Upgrade as you go" policies leave long tails of half-completed conversions that make the codebase harder to ramp new devs on. You'll also never finish the conversion because there's no guarantee that product focus will walk every part of the codebase with any regularity. Some product areas get left alone for years and years and years.
It's either important enough to cut over to the new policy in one concerted project, or it's not important.
- steveBK123 3y agoYea it’s atrocious as management is basically derelict in planning. They are relying on random unrelated work tasks to trigger these unplanned work time bombs all over the code base . Either some new standard is important and the code should be updated, or not. Just relying on randomness and slowing down urgent work ain’t a plan.