I like the idea of filing an issue for things, but I've found in practice those issues never get done (they tend to be hard to prioritize over other biz-facing features) & tend to clutter up backlogs.
Generally speaking the size of a TODO item tends to be quite small, probably too small to be encapsulated as a single issue in a task tracker, so if every "TODO" item became an issue there's a very real risk of being killed by a thousand paper cuts" as well.
TODO's in code can have the same issue around "never getting done", but at least then while working in an area of code you're forced to see related TODO items in that area that can give you context around shortcomings or areas in which that code can/should be improved.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like the idea of filing an issue for things, but I've found in practice those issues never get done (they tend to be hard to prioritize over other biz-facing features) & tend to clutter up backlogs.
Generally speaking the size of a TODO item tends to be quite small, probably too small to be encapsulated as a single issue in a task tracker, so if every "TODO" item became an issue there's a very real risk of being killed by a thousand paper cuts" as well.
TODO's in code can have the same issue around "never getting done", but at least then while working in an area of code you're forced to see related TODO items in that area that can give you context around shortcomings or areas in which that code can/should be improved.