[mrbuzzinfrog]

IMO these are anti-patterns that makes code smelly.

A practice I like to follow is to document "hacks" and create tickets for TODO items. In my experience, this has scaled better with the growth of the team and also allows for knowledge sharing and brainstorming when planning.

For TODO items I used the "eisenhower matrix" to decide if I should create a ticket for it or not. Where TODO items that are not "urgent" nor "important" are simply ignored until they reemerge again.

There are few phrases that I like to mention when I see devs add TODO comments:

- if in doubt leave it out

- every line of code is a potential liability that needs to be maintain and tested

- in the future requirements may be different or no longer relevant