4 ms·

Later: FIXMEs aren't for doing. FIXMEs are comments describing how a piece of code is less than ideal. The code works, of course, because we never commit non-wo

by qwery 1y ago

Later: FIXMEs aren't for doing. FIXMEs are comments describing how a piece of code is less than ideal. The code works, of course, because we never commit non-working code -- it could be improved, but it's not broken. The actual fix me is a compiler error.

johnnyanmac 1y ago
Later: some compiler errors are just warnings. If you really know what you're doing, you can suppress them and go about your merry day. You're not paid to make correct code; just "shippable" code. Anyways, I'd be happy with a structure like - "NIT" that acts more like notes for correct implementations used for highlighting potentially better structures or optimization to consider farther down the line - TODO for issues that can or will become issues later on, but are otherwise functional for prototyping purposes. I don't think every TODO needs to be corrected, but you should have a refactoring day every period where you address most of these TODOS. - FIXME for critical or showstopper level issues, but you need to clock out for the day. There shouldn't be any FIXME in a stable branch of code. Arguably a FIXME shouldn't persist for more than a few commits.
- alanbernstein 1y ago
  Whatever theme/packages I use in Emacs have been highlighting NOTE, TODO, FIXME in comments for at least the last 10 years, so that's what I use.
  - sslayer 1y ago
    My code contains no NOTEs,TODOs,FIXMEs or Comments, for as Programmer, I have transcended space and time to the final abstraction, and no longer write any code, only long complicated manual procedures, which I then outsource to third parties, who in true programming fashion use AI.
  - johnnyanmac 1y ago
    NOTE is a good word for it too. Never saw it in the wild myself, but I'll adopt that (easier than explaining what NIT is)
    - CRConrad 1y ago
      You don't need to be accused of being a nit-picker all that many times to figure out what a nit is. So the label is kind of useful: for flushing out the people who need it explained -- now you know sho's sloppy enough to be worth being wary about.

by qwery 1y ago

johnnyanmac 1y ago

Later: some compiler errors are just warnings. If you really know what you're doing, you can suppress them and go about your merry day. You're not paid to make correct code; just "shippable" code. Anyways, I'd be happy with a structure like - "NIT" that acts more like notes for correct implementations used for highlighting potentially better structures or optimization to consider farther down the line - TODO for issues that can or will become issues later on, but are otherwise functional for prototyping purposes. I don't think every TODO needs to be corrected, but you should have a refactoring day every period where you address most of these TODOS. - FIXME for critical or showstopper level issues, but you need to clock out for the day. There shouldn't be any FIXME in a stable branch of code. Arguably a FIXME shouldn't persist for more than a few commits.

alanbernstein 1y ago
Whatever theme/packages I use in Emacs have been highlighting NOTE, TODO, FIXME in comments for at least the last 10 years, so that's what I use.
- sslayer 1y ago
  My code contains no NOTEs,TODOs,FIXMEs or Comments, for as Programmer, I have transcended space and time to the final abstraction, and no longer write any code, only long complicated manual procedures, which I then outsource to third parties, who in true programming fashion use AI.
- johnnyanmac 1y ago
  NOTE is a good word for it too. Never saw it in the wild myself, but I'll adopt that (easier than explaining what NIT is)
  - CRConrad 1y ago
    You don't need to be accused of being a nit-picker all that many times to figure out what a nit is. So the label is kind of useful: for flushing out the people who need it explained -- now you know sho's sloppy enough to be worth being wary about.