Hacker News new | ask | show | jobs
by drsim 4853 days ago
A combo of doc + a branch commit would be spot on.

You're right on the code bomb problem, but I think a good review involves making a judgement on the entire codebase. Something may be the 'right' thing to do but completely uneconomical due to dependencies.

Understanding the impact of a recommendation leads to a valuable refactor or rewrite call that developers often have to make on a mature ecosystem.