StatementI often find myself still writing the following statement all over my code:// TODO: (the work that needs done)I do this in order to flag that I need to come back and do something later on. It often happens when the functionality of the code is dictated by other code that will be written later on. I did a quick Google search and took the first two results about this...The first result I found explains that this is a valid way of doing things, and is the first result that shows up in Google:How do you flag code...Then, another result I found suggested something about that a Task List could be used as an alternative...Creating Task Lists with Visual Studio...The problem I have with both of these is that they are both 7+ years old, and I am exploring what has changed between now and then.QuestionIs writing TODO, still a valid way of doing things?
Does anybody still use TODO for writing code later on?
c#;design;visual studio;comments
If you are into TDD, I suggest you write up a test which will fail until the functionality gets implemented.The only downside I can see is if you are a somewhat lazy function such failing tests will contribute a lot of noise to runs and may hide actual failures behind all that.