Forgot your password?
typodupeerror
Bug Programming

Ask Slashdot: Should Developers Fix Bugs They Cause On Their Own Time? 716

Posted by Soulskill
from the 10-of-10-employed-developers-say-no dept.
Bizzeh writes "Today my boss came to me with what he thought to be a valid point and analogy. A builder builds a wall. A week later, bricks begin to fall out of the bottom, but he continues to build the wall higher. In most cases, he would have to replace those lower bricks at his own expense and on his own time. Comparatively: A software developer writes a piece of software. When bugs are discovered, the developer is paid to fix them by the employer and on the employer's time. I didn't know how to refute the analogy at the time, but it did make me think: why are bugs in software treated differently in this way?"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: Should Developers Fix Bugs They Cause On Their Own Time?

Comments Filter:
  • by RichMan (8097) on Tuesday February 11, 2014 @06:55PM (#46223155)

    Bugs are escapes from the QA process. The QA people can fix them on their own time as the fault is in the QA process not the developer. :)

  • by Anonymous Coward on Tuesday February 11, 2014 @07:01PM (#46223291)

    The builder was probably commissioned specifically to build the wall, as well.

    The developer was probably commissioned to build something with nebulous requirements like "keeping the Huns out", and this was the only idea his boss could understand to sign off on.

  • by msauve (701917) on Tuesday February 11, 2014 @07:16PM (#46223505)
    "Mother did it need to be so high?" - Roger Waters.
  • by king neckbeard (1801738) on Tuesday February 11, 2014 @07:18PM (#46223533)
    Tell your boss he should be fired. If he's going to make bad analogies, they should at least involve cars.
  • by Impy the Impiuos Imp (442658) on Tuesday February 11, 2014 @07:23PM (#46223599) Journal

    To all programmers out there, I'll fix your bugs at 5x the rate you do, for a mere 2x your salary. I specialize in array overruns because you're an idiot, pointer misalignments throwing low-level hardware exceptions because you're an idiot, calculation errors due to incorrect operator precedence and casting at inappropriate stages because you're an idiot, and multithread bugs because you're an idiot.

  • by RabidReindeer (2625839) on Tuesday February 11, 2014 @07:37PM (#46223749)

    To all programmers out there, I'll fix your bugs at 5x the rate you do, for a mere 2x your salary. I specialize in array overruns because you're an idiot, pointer misalignments throwing low-level hardware exceptions because you're an idiot, calculation errors due to incorrect operator precedence and casting at inappropriate stages because you're an idiot, and multithread bugs because you're an idiot.

    Well, I'm an idiot, anyway. None of the sins you listed are commonly committed by me, however. In some cases they're impossible using the language and tools I'm presently using, but in most cases, because I've always been rather paranoid about the low-level stuff since I did a lot of OS internal work where that sort of thing could send an entire company home for the afternoon.

    Not to say that I do bug-free work, just am more subtle in my bugs.

    However, the last major corporate job I had, didn't want that level of quality and frequently dinged me for it. All they wanted was for me to "Git 'R Dun!"

    It's not like they were a major financial institution or anything. Oh wait...

  • by Anonymous Coward on Tuesday February 11, 2014 @10:42PM (#46225237)

    > An old truck of mine died one day on the highway, leaving a toll booth.

    Please send my condolences to the toll booth. The loss of a parent can be devastating.

We are Microsoft. Unix is irrelevant. Openness is futile. Prepare to be assimilated.

Working...