Just going to pick a single nit. > you don’t want your project to end up like the Linux codebase with 3000+ TODOs dating back over a decade. Why don't I? TODO

Just going to pick a single nit. > you don’t want your project to end up like the Linux codebase with 3000+ TODOs dating back over a decade. Why don't I? TODOs capture a lot of context that would otherwise be inappropriate or unseen in a comment. They're in all caps and they stand out and draw the reader's eye. They can be completely out of context, whereas comments are typically extremely contextual. They often help explain cases not covered, paths not supported, missing functionality or notes for future contributors. Splitting them into even more comments just makes them harder to find and reason about. When you're writing a TODO, you don't want to stop to smell the roses, thinking about what the future may hold, you just want to blot down the thought in your head and finish the task at hand. Not to mention that in reality it's quite reasonable: https://livegrep.com/search/linux?q=TODO&fold_case=false&regex=false&context=true https://livegrep.com/search/linux?q=TODO&fold_case=false&reg... You be the judge.