Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Comment Re:Nonsense (Score 1) 763

This in itself was surprising because he often deployed changes without checking in code. We tried many times to tell him never to do that.

At the risk of stating the obvious: this should be impossible. Your deployment path should go through your version control system, not exist in parallel with it.

How do you respond to someone like that?

Peer reviewed code is a good start. Not hierarchical necessarily, just make sure that whenever somebody codes something it gets read by at least one other person before it's deployed.

"For the love of phlegm...a stupid wall of death rays. How tacky can ya get?" - Post Brothers comics