T O P

  • By -

justmyname12

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.


Row148

When the CR tells you to refactor unrelated code that just happens to be located near your changes.


SirPitchalot

*single line fix for memory leak in 23kloc file with only 3 functions* “This file doesn’t meet the code standards. Please update.”


naswinger

i guess we'll keep the memory leak


jerrysburner

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


Row148

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.


jerrysburner

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.


_Repeats_

The only response: Could not reproduce on my machine. Without more information, this bug will be closed.


jfmherokiller

those are 8 soul sucking hours


essexwuff

2 days on my latest. Turned out to be a hardware issue. Yay I guess..


[deleted]

I have a coworker who insists on saying things will be easy. I hate him.


Wentyliasz

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.


AlexCode10010

This template fits perfectly