3 ms·
Eh, depends on what you’re optimizing for. For fixing the bug as quickly as possible, yes. For spreading that context throughout the team or getting other featu
by mandelbrotwurst 5y ago
Eh, depends on what you’re optimizing for. For fixing the bug as quickly as possible, yes. For spreading that context throughout the team or getting other features out that the person with context is best equipped to ship, no.
- kawsper 5y agoIf it is just reorganisation of project files then the fastest way to fix the bug would likely be to just revert the commits.
- alexeldeib 5y agoConsequently, this highlights why the first person may have an incentive to fix it: if their code gets reverted to fix the issue, they will definitionally be forced to rework it before they’re able to merge again.