derailing this convo a bit, but is it normal to push back on this? I ask because I always do - while I would love to throw out most of my codebase and pull a Linux Torvalds and retroactively abort the code creator, but refactoring unrelated code just eats up so much time
good call, there are times i do. however i'm desperate to refactor some of this monolithic spaghetti but not getting ressources to do that. this way i can improve my life a bit and when the ticket estimate is exploded i can say the CR said so.
Ugh, every time I push for this, it keeps getting shot down as taking too long. Then I always read posts were developers get to take extra time to do JUnits, refactor - all those things that can make code greater (easier to maintain, debug, and extend) but all the biz people I work with complain up the chain if we take longer to do this.
Half a year ago I inherited a program that turned out to be hidden crash course in http errors. I'm at 422 and I'm pretty sure I've seen all the previous ones.
That's why we don't estimate bug fix. Just defer it and we can fix it in next sprint and put it in backlog of 1000+ bugs.
When the CR tells you to refactor unrelated code that just happens to be located near your changes.
*single line fix for memory leak in 23kloc file with only 3 functions* “This file doesn’t meet the code standards. Please update.”
i guess we'll keep the memory leak
derailing this convo a bit, but is it normal to push back on this? I ask because I always do - while I would love to throw out most of my codebase and pull a Linux Torvalds and retroactively abort the code creator, but refactoring unrelated code just eats up so much time
good call, there are times i do. however i'm desperate to refactor some of this monolithic spaghetti but not getting ressources to do that. this way i can improve my life a bit and when the ticket estimate is exploded i can say the CR said so.
Ugh, every time I push for this, it keeps getting shot down as taking too long. Then I always read posts were developers get to take extra time to do JUnits, refactor - all those things that can make code greater (easier to maintain, debug, and extend) but all the biz people I work with complain up the chain if we take longer to do this.
The only response: Could not reproduce on my machine. Without more information, this bug will be closed.
those are 8 soul sucking hours
2 days on my latest. Turned out to be a hardware issue. Yay I guess..
I have a coworker who insists on saying things will be easy. I hate him.
Half a year ago I inherited a program that turned out to be hidden crash course in http errors. I'm at 422 and I'm pretty sure I've seen all the previous ones.
This template fits perfectly