3 ms·
If you think that is horrible, let me tell you a story about the opposite approach: There is very successful company, let's call them "LEG", that makes compute
by panpanna 7y ago
If you think that is horrible, let me tell you a story about the opposite approach:
There is very successful company, let's call them "LEG", that makes computer thingies. In order to improve customer confidence, "LEG" has adopted a very strict release policy: all instances of TODO, FIXME, BUG and ERROR are removed before a release.
If you have a variable called "error", automated tools will flag it and you will have to explain to your boss why you could not have used any other name.
- sweden 7y agoWhich makes sense. Why are you making a customer release with outstanding TODOs/FIXMEs/BUGs/Whatever in the code? Are there things left to do? Are you delivering something incomplete to the customer while saying it's bug free and feature complete? You need to make a decision whether to actually fix what you intended to fix or to judge that it's not relevant anymore. The script is letting you know that there are outstanding things in the code that might have been forgotten. If you are the owner of those TODOs and choose to just delete the comment in order not to have any extra work, then maybe someone in your company should review your presence there.
- panpanna 7y agoLet me clarify: they are not fixing the issues, just hiding them from customers. Are these important issues that should have been fixed or just small good-to-have things? The answer is: yes