3 ms·
I don't agree with making tickets to come back and fix things. Lots of times changing a line in a file points out how smelly it is. If it can be fixed there, I
by amw-zero 9y ago
I don't agree with making tickets to come back and fix things. Lots of times changing a line in a file points out how smelly it is. If it can be fixed there, I say give it a shot.
Sometimes "I'll open a ticket" is code for "I'd love to do this, but I'm never going to."
- hinkley 9y agoTranslated again: “I’d love to be perceived as willing to do this, but I’m never going to.” I got a big dose of this on a project. Requirements got hung up for weeks and the do it later crowd simply had no idea what to work on. To me this means all the stuff they “didn’t have time for” was stuff they couldn’t be bothered with. If you don’t tell me what to work on I can think of ten different things that are about to break.
- Patrick_Devine 9y agoI think it cuts both ways. Yes, it's definitely easier to change code while you're already there, but on the flip side, it can potentially create a huge burden for the programmer. A simple change might turn into a multi-day slog when there are more pressing things that need attention.