Comment

Comment by stephenhandley

Effective TODOs capture a code-level design tradeoff and any associated debt which

- won't have sufficient positive impact on the bug/feature you are working on

- you don't have time to address at that point in time

- are significant enough to require pay down later

How to address them in terms of tooling and process is a way bigger question

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton