Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

18
  • 7
    From an OO perspective, both scenarios become: "Team member ain't around no mo'." Isn't "better employment op" just a subclass of "unfortunate accident?" Commented Jan 3, 2011 at 22:42
  • 4
    @Yar: yes, though I guess you could still ask someone who found "better employment" to come back for more money... no amount of money is going to bring him back from under a bus :-) Commented Jan 3, 2011 at 23:33
  • 4
    I encourage the devs in my group to ask/pair with the original author that way you get the faster bug fix along with some distribution of knowledge. Commented Jan 4, 2011 at 7:44
  • 19
    You know, this is one of those things that are so wonderful in theory but that rarely works in practice. It's because of the tragedy of the commons. If everything is everyone's responsibility, then nothing is anyone's responsibility because anything is someone else's responsibility. Psychologists call it "social loafing". You need a balance of individual responsibility and team responsibility. Commented Jan 4, 2011 at 21:38
  • 4
    I'd argue against that @Jason. If it is the case, you need better employees, smaller teams. Peer pressure should be able to keep that in check, as long as the team isn't a bunch of flakes. Team Ownership does not beget lack of individual responsibility. Commented Jan 4, 2011 at 21:47