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.

4
  • 10
    +1: For ...Good programmers spend a lot of time dealing with other programmers' broken code anyway. Commented Jan 8, 2013 at 2:32
  • 3
    +1 Best answer. Especially pointing out that one dev committing a build-breaking bug negatively impacts everybody. Commented Jan 8, 2013 at 3:48
  • Been in that situation, turned out out best two programmers were full time used to review and correct other people's code. Sure the code quality on the VCS was good but morale for these two dwindled faster than a toilet flush. What started as a seemingly good idea turned to nightmare when these two ran out the door to places where they could get, say, more creative tasks. Commented Sep 9, 2016 at 15:08
  • 1
    That's a good point, @Newtopian. The places where I've seen this succeed have more of a microservice model, and only one scrum team has commit access to any given microservice, but responsibility is spread around for the system as a whole. If you don't have at least a couple experienced programmers per scrum team your hiring practices need improving. Commented Sep 9, 2016 at 16:45