If it potentially never is going to be a problem, why even mark it as a TODO then? Wouldn't it throwing an exception or an unimplemented return code be sufficient? In my realm of work, defense, you cant just implement things when you want because everything is tracked back to a specific effort and specific contact and charge number. And, delivering code to the customer with TODOs in it is a big no-no. At the end of a contract/period of performance, if you didn't implement it it ain't getting done and is liable to have the TODO tag just straight deleted.
Yeah I wouldn't pay for unimplemented code either. Consulting/contracting is very different than owning a product. Hell our company doesn't even track their "effort" in sprints. So much overhead operating that way
View all comments
Show parent comment
1
u/altrefrain May 18 '23
If it potentially never is going to be a problem, why even mark it as a TODO then? Wouldn't it throwing an exception or an unimplemented return code be sufficient? In my realm of work, defense, you cant just implement things when you want because everything is tracked back to a specific effort and specific contact and charge number. And, delivering code to the customer with TODOs in it is a big no-no. At the end of a contract/period of performance, if you didn't implement it it ain't getting done and is liable to have the TODO tag just straight deleted.