// TODO:
| Look closely, little boy
| This is where the
| madness begins.

  • 4
    With that last tag, you're looking to start a flame war, aren't you?

    On the point, if there's a simple TODO left like this with no further explanation, I'd expect that the issues is self-explanatory when you look at what's there.
  • 2
    I want to push that | over a nudge... damn thing doesn't line up.
  • 0
    While I agree postponing stuff isn't great, sometimes it's better to take a little more incremental approach. Then, the TODOs are pretty neat. That way it also works more like a police man rather than procrastination.
  • 1
    Kotlins TODO() not yet implemented exception thrower is neater for that purpose. After all if something important and obvious is missing you should eighter make sure with a comment what it is if it should run or the TODO above to make it fail.
  • 2
    Any commit containing a TODO should be rejected by CI imo
  • 1
    I usually just write a test

    assertTrue(false, "don't forget to rename cuntcream to female genital hygiene product before merging")

    That way my "todo" will get stuck in the testing pipeline if I accidentally push it.
  • 0
    @bittersweet very subtle. But I like the idea!
Add Comment