I think you’re getting at a deeper issue. The need for bug-for-bug parity intern... | Hacker News

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

		Retric on Jan 31, 2022 \| parent \| context \| favorite \| on: Tech debt gets worse before it gets better I think you’re getting at a deeper issue. The need for bug-for-bug parity internally is itself a sign of technical debt. At this point we can’t for example fix historical calendars, so all highly accurate date and time related code is going to be complicated and full of edge cases. Such code is in effect an interest payment on society’s existing technical debt. So, the temptation to refactor such code is generally attacking the wrong side of a problem. The best approach may be to quarantine such code/systems and try and minimize the impact of such issues.

dilyevsky on Jan 31, 2022 [–]

I could have said “feature parity” it doesn’t change the argument much.

> The best approach may be to quarantine such code/systems and try and minimize the impact of such issues.

That’s the old Google’s “v2 is wip v1 is obsolete”. Works ok internally, externally not so much

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