Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Submission + - Should developers fix bugs in their own time? 7

Bizzeh writes: Today my boss came to me with what he thought to be a valid point and analogy. If a builder builds a wall, and a week later, bricks begin to fall out of the bottom, but he continues to build the wall higher, he would have to replace those lower bricks he did not place correctly at his own expense and in his own time. When a software developer writes a piece of software, when bugs are discovered, they are paid to fix them by the company and on the companies 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 was created for logged-in users only, but now has been archived. No new comments can be posted.

Should developers fix bugs in their own time?

Comments Filter:
  • 1. Software developers have no professional engineering qualification; a double edge sword for sure. 2. Managers often do not listen to developers' designs and concerns, often cutting corners with development time and quality assurance, in the name of cost cutting.

  • That analogy is so flawed as to make me wonder if your boss should be managing developers. Make sure he knows that you don't work for free, and that no software developer worth a damn is going to either.

    Fixing bugs is not 'replacing bad bricks', and software engineering is not as simple as looking at an opening and seeing how many lines of code will fill it.

    • by Bizzeh ( 851225 )

      I never said i agreed with my boss, i said i lacked a valid argument to the analogy, and/or an analogy of my own to counter with.

  • Both achowe and 3vi1 have very good points. To expand on one of 3vi1's points (with which I agree completely), volunteer, open-source development counts as a hobby. Good devs don't work for free.

    Sure, everyone makes mistakes, but if customer A wants this feature and customer B wants that feature, the design can change and bugs will result. The analogy here would be if a bricklayer lays some bricks and the architect says, "I changed my mind, let's use marble instead," the bricklayer is paid to replace
  • Boss: how's the project going?
    Employee: not bad, I have formally verified 75% of the model domain. In 15/20 years, once the rest of the code, the database and the operating system bits are formally verified, we can ship it.

  • It is often the case that an employee of a company signs an agreement with the employer indicating that all of the source code a developer produces belongs to the company. There is also the "Intellectual Property" agreements that are signed by the employee which indicate that all ideas generated by a developer belong to the company. Those two agreements indicate that once the source code is typed into the computer, it is then a company possession along with the ideas that generated the source code. A logica

If a 6600 used paper tape instead of core memory, it would use up tape at about 30 miles/second. -- Grishman, Assembly Language Programming