Thelie@sh.itjust.works to Programmer Humor@programming.devEnglish · 3 months agoProgramming as a hobby means I can do whatever I want!sh.itjust.worksimagemessage-square24fedilinkarrow-up1235arrow-down18
arrow-up1227arrow-down1imageProgramming as a hobby means I can do whatever I want!sh.itjust.worksThelie@sh.itjust.works to Programmer Humor@programming.devEnglish · 3 months agomessage-square24fedilink
minus-squaremagic_lobster_party@kbin.runlinkfedilinkarrow-up14arrow-down2·3 months ago todos I found a simple trick against this: just remove them. Accept it ain’t gonna happen man.
minus-squareAggressivelyPassive@feddit.delinkfedilinkarrow-up4·3 months agoWell, yes, but the underlying issues still persist, so it’s not exactly a sustainable strategy.
minus-squaremagic_lobster_party@kbin.runlinkfedilinkarrow-up3·3 months agoIt’s mostly a joke, but often when I find todos they’re so old they’re no longer relevant. Of course you shouldn’t blindly remove todos.
minus-squarefrezik@midwest.sociallinkfedilinkarrow-up1·3 months agoDon’t just put “TODO”. If they’re in the final pull request, they need to mention a ticket that’s intended to fix that TODO. If you/your team decides it’s not important, then remove it. Either way, you’re required to do something with it.
I found a simple trick against this: just remove them. Accept it ain’t gonna happen man.
Well, yes, but the underlying issues still persist, so it’s not exactly a sustainable strategy.
It’s mostly a joke, but often when I find todos they’re so old they’re no longer relevant.
Of course you shouldn’t blindly remove todos.
Don’t just put “TODO”. If they’re in the final pull request, they need to mention a ticket that’s intended to fix that TODO. If you/your team decides it’s not important, then remove it. Either way, you’re required to do something with it.