Timeline for Should your best programmers have to check everyone else's code into source control?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 9, 2016 at 16:45 | comment | added | Karl Bielefeldt | 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. | |
| Sep 9, 2016 at 15:08 | comment | added | Newtopian | 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. | |
| Jan 17, 2013 at 19:19 | vote | accept | GlenPeterson | ||
| Jan 8, 2013 at 3:48 | comment | added | Evan Plaice | +1 Best answer. Especially pointing out that one dev committing a build-breaking bug negatively impacts everybody. | |
| Jan 8, 2013 at 2:32 | comment | added | Jim G. | +1: For ...Good programmers spend a lot of time dealing with other programmers' broken code anyway. | |
| Jan 7, 2013 at 22:42 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |