3 ms·
Not all developers make positive contributions, but no single developer in a team of developers can make a non-positive contribution. They can't, because as a
by jasonlotito 10y ago
Not all developers make positive contributions, but no single developer in a team of developers can make a non-positive contribution. They can't, because as a team, you've decided to allow this person to make contributions alone. You need to own that contribution. If you don't want to that responsibility, there is a solution: code reviews.
Anything that gets submitted is literally something you've agreed to support and are okay with being in the code base.
- d_rwin 10y agoI have seen the type always conform to a style or structure. The designers like to talk to design bent leads on devevelopment and manage only a subset of issues that could materialise. A dev team for three or more years brings a better structure to code and developement. Just the fact, the leisure time well spent in code and banter bring enough structure to the team. I guess you have to know your team better than your desk-jockeys.
- jasonlotito 10y agoI'm honestly not sure what you mean here. I can't make sense of it.
- d_rwin 10y agoThanks Jason. It is a little vague, I admit. The team strength in any scope or structure, well defined is 'A Win'.
- plorkyeran 10y agoProducing a lot of code which has to be reviewed without ever actually landing any of it is itself a non-positive contribution. Code reviews are wonderful and I'd never want to go back to working on a team that didn't do them, but they do take time from the reviewers.
- jasonlotito 10y agoThat's true, though I was specifically focused on actual code contributions that make it into a production branch.