TLDR
Many codebases are guilty of having TODOs linger around while nobody knows who’s responsible for a TODO or even has the required context to tackle it. It makes more sense to extract TODOs to a centralized interface that allows you to actively manage them and add metadata such as context, feature descriptions, requirements, or even relevant code snippets. This article discusses the different reasons why software engineers use TODOs in projects. The most important problem with TODOs is their lack of context.via the TL;DR App
no story
Written by alexomeyer | Co-founder & CEO at stepsize.com, creating the AI companion for software projects
