I want clean, readable code with proper documentation and at least a bit of internal consistency and not the shoehorned mess of hacks, todos and weird corner cases.

[–] magic_lobster_party@kbin.run 13 points 5 months ago (2 children)

todos

I found a simple trick against this: just remove them. Accept it ain’t gonna happen man.

[–] agressivelyPassive@feddit.de 5 points 5 months ago (1 children)

Well, yes, but the underlying issues still persist, so it's not exactly a sustainable strategy.

[–] magic_lobster_party@kbin.run 3 points 5 months ago

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.

[–] frezik@midwest.social 1 points 5 months ago* (last edited 5 months ago)

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 and close out the ticket. Either way, you're required to do something with it.