by dpJudas » Thu Jul 19, 2018 5:55 pm
Is this just, like, if an issue tracker exists, it totally drives you nuts in an "I can't help it" way? 'Cause if so... well, don't drive yourself nuts over it*!
I think this may just be the first time I've heard of that. Most devs I know (including myself) are the opposite -- if an issue isn't filed away somewhere (even if it's in the "this will practically never get done" backlog), it's like a spectre hovering about.
Some people they love order, they love the thought of showing up at work, open the issue tracker and look at what is at the top of the priority list and then just happy as a clam go work on that ticket. Might even get a feeling of satisfaction as they see the list grow shorter and see things get done. I have a coworker that is like this and he's the best on our team to grind bugs and add smaller features that fit into tickets.
I'm very much not like that. I feel like a robot under such conditions and want to kill myself. Generally speaking, I'm good at making large changes (or writing entirely new software) that may take significant time to implement with barely existing specs. Stuff that in agile slave-worker systems would be labeled as an epic and be blocked via daily slaveups. Doing maintenance work for me is nothing but a chore and the last thing I need is to have a list of chores. To me that's what an issue tracker is.
In a professional team I'm the developer that somehow "forgets" to create tickets and codes on stuff I'm not really supposed to be coding on. What I feel like coding on varies greatly from day to day, but ultimately half of what I implement would not ever get done if you strictly followed the backlog. And for the same reason all bugs related to renderhacks are filed under "renderhacks not implemented" in my head - I don't need to see all the variations that would need testing if I tried to implement it one day. If anything, it would just discourage me.
So it isn't so much a question of me not wanting to fix all bugs in softpoly, but rather it is colored by the mood I have on any given day. Some people will call that unprofessional, but it is the same thing that gives me the energy and time to think about and solve other complex problems. Incidentally, the guy on our team that is a master ticker grinder is absolutely horrible at what I do. There isn't the crime he won't do on a codebase if it allows him to fix a ticket fast.
Sorry for the wall of text, but hopefully that explains why,
to me, issue trackers isn't an aid.
[quote]Is this just, like, if an issue tracker exists, it totally drives you nuts in an "I can't help it" way? 'Cause if so... well, don't drive yourself nuts over it*! :P
I think this may just be the first time I've heard of that. Most devs I know (including myself) are the opposite -- if an issue isn't filed away somewhere (even if it's in the "this will practically never get done" backlog), it's like a spectre hovering about.[/quote]
Some people they love order, they love the thought of showing up at work, open the issue tracker and look at what is at the top of the priority list and then just happy as a clam go work on that ticket. Might even get a feeling of satisfaction as they see the list grow shorter and see things get done. I have a coworker that is like this and he's the best on our team to grind bugs and add smaller features that fit into tickets.
I'm very much not like that. I feel like a robot under such conditions and want to kill myself. Generally speaking, I'm good at making large changes (or writing entirely new software) that may take significant time to implement with barely existing specs. Stuff that in agile slave-worker systems would be labeled as an epic and be blocked via daily slaveups. Doing maintenance work for me is nothing but a chore and the last thing I need is to have a list of chores. To me that's what an issue tracker is.
In a professional team I'm the developer that somehow "forgets" to create tickets and codes on stuff I'm not really supposed to be coding on. What I feel like coding on varies greatly from day to day, but ultimately half of what I implement would not ever get done if you strictly followed the backlog. And for the same reason all bugs related to renderhacks are filed under "renderhacks not implemented" in my head - I don't need to see all the variations that would need testing if I tried to implement it one day. If anything, it would just discourage me. :p
So it isn't so much a question of me not wanting to fix all bugs in softpoly, but rather it is colored by the mood I have on any given day. Some people will call that unprofessional, but it is the same thing that gives me the energy and time to think about and solve other complex problems. Incidentally, the guy on our team that is a master ticker grinder is absolutely horrible at what I do. There isn't the crime he won't do on a codebase if it allows him to fix a ticket fast.
Sorry for the wall of text, but hopefully that explains why, [i]to me[/i], issue trackers isn't an aid. :)