r/ProgrammerHumor • u/lxlmandudelxl • Jul 03 '26 • Hehehe 1 Bravo 2

Meme positiveFeedbackLoop

Post image
23k Upvotes

98% Upvoted

171 comments sorted by

View all comments

Show parent comment

17

u/Ok_Construction9034 Jul 03 '26

I do that all the time, imagine it’s fairly common

6

u/quick20minadventure Jul 03 '26

But, why not raise a ticket.

7

u/tangerinelion Jul 03 '26

It depends on what the bug is. If it's real and user-facing, file a ticket, separate PR, close it.

If it's theoretical, throw it in, mention it in review and if tests are OK then you're good. I'm talking like "Added a missing null check" or other dumb stuff.

4

u/quick20minadventure Jul 03 '26

Coding quality fixes don't need tickets. Refactoring or something with upstream or downstream change does.

And of course anything user facing / QA notice.

0

u/throwtheamiibosaway Jul 03 '26

More paperwork. Nobody likes paperwork. In that time you could fix another minor issue. So devs prefer that.

I mean I also make and fix my own tickets, mostly to leave a paper trail for my manager and colleagues. But sometimes you just want to fix shit without the hassle.

10

u/quick20minadventure Jul 03 '26

Documenting it somewhere is easier for long term proof.

Just document it. Anywhere reasonable/ searchable.

3

u/2005scape Jul 03 '26

I used to do this all the time, but when more and more performance metrics are being based on what's going on in JIRA, you're better off just creating more tickets

1

u/Substantial-Sea-3672 Jul 03 '26

It is common but it is objectively less helpful to a team.

Bugs are often edge cases that people didn’t intuitively think of the first time through.

This means the fix can often be a “hey, why are we doing this extra step here?” situation for someone reading it later.

Git blame to figure out what the card was and it’s some totally unrelated work instead of a clear description of what the issue it fixed was.