Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> And that's how the long tail becomes long tail.

Not really.

Developers should only touch production code if there is a good business reason to touch it, whether fixing a bug or adding a feature. If there is no good reason to touch a bit of code, you should not be touching it. Otherwise you're just adding noise to the audit trail, perhaps along with bugs in otherwise perfectly fine code, without any justification.

The long tail is a long tail because there are no bugs not reasons to mess around in those parts of the code. Feeling adventurous is not a good reason to mess with it. If you have to implement a feature or fix a bug, complaining that it's old code won't make things go away.



> If you have to implement a feature or fix a bug, complaining that it's old code won't make things go away.

sure, but you might decide to work on a different feature/bug because this part of the code is too arcane to touch




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: