chimerror

I'm Kitty (and so can you!)

  • she/her

Just a leopard from Seattle who sometimes makes games when she remembers to.


I have a lot of TODOs in my source code so I can just write little bugs and thoughts and questions down to get them out of my head so I can move on.

But as I'm beginning to get into a release cycle, I have the sense that I should start prioritizing TODOs. At first, this was just so I can add TODOs that I meant to deal with before I made my commit. Then I realized I can go even further.

So... the number of times I say "TODO" is how big a priority that is:

  • TODO: Whatever, I'll get to it
  • TODOTODO: Fix this before the next release
  • TODOTODOTODO: Fix this before committing

This is likely a sign I should look into an honest-to-god issue tracker lol


You must log in to comment.

in reply to @chimerror's post:

Oh rad! I use an issue tracker in tandem with writing TODOs in my code . . . mostly so that I can keep info I might forget close to where I'm actually working

But I also document more than most people would, so it may be overkill! 😅