Re:Google takes the pain out of code reviews, with 97% dev s...
by throwawaaarrgh on Monday December 04, 2023 @03:14PM
(#38522450)
> it starts showing cracks on a long enough timeline in sufficiently large or complex projects
Show me a project which this doesn't happen to on a long timeline and I'll show you a project with no users and perfect programmers.
Entropy is unavoidable. It will eventually degrade despite your best efforts and in the meantime you aren't benefiting from a working feature. We should try to delay software entropy as much as practical, but not at the expense of shipping.
Basically there is a balance to strike. I don't have a formula for it, but I do know that merging often ends up being more valuable than merging later just to ensure clean code. Working features are more valuable than a mess. A mess sucks, so we should try to avoid it, but the world runs on messes, not clean code.
Show me a project which this doesn't happen to on a long timeline and I'll show you a project with no users and perfect programmers.
Entropy is unavoidable. It will eventually degrade despite your best efforts and in the meantime you aren't benefiting from a working feature. We should try to delay software entropy as much as practical, but not at the expense of shipping.
Basically there is a balance to strike. I don't have a formula for it, but I do know that merging often ends up being more valuable than merging later just to ensure clean code. Working features are more valuable than a mess. A mess sucks, so we should try to avoid it, but the world runs on messes, not clean code.