One of the challenges of working on a time-sensitive project is balancing getting something working while also keeping track of the various document, tasks, issues, and general project TODOs.
I don’t know what this looks like for you. But for me. project TODOs usually fall into one of two groups:
- I need to go back and document a file, class, property (or properties), functions, or module.
- There are places that I know need to be refactored. Perhaps a function needs to be split into two methods. Perhaps I need to rework an algorithm. Whatever the case, there’s something that needs to be done before I’m happy with it being final.
And when that’s the case, it’s easy to forget to come back to these areas in the code and rework them as you see fit.
This is where the idea of project TODOs come in, but I even think we can take it a bit further.