Re:What's better about Ruby than Python? - comp.lang.python
by derefr on Thursday August 26, 2010 @11:30PM
(#1637926)
In what situation is it actually a good idea to employ a large number of bad programmers, rather than a small number of good ones? We shouldn't be making trade-offs for the sake of bad ideas ;)
[ Parent
| on HN ]
Re:What's better about Ruby than Python? - comp.lang.python
by acdha on Friday August 27, 2010 @09:52AM
(#1638800)
There's a distinction to be made between preventing risky behaviour and relying only on a programmer's good judgement to avoid mistakes. Even if your team is solely good programmers there's a lot to be said for discouraging unsafe behaviour by default since anyone can have a bad day, distraction, etc.
I view this situation as somewhat analogous to having guards on power tools: even a highly skilled operator doesn't want to rely on always doing something perfectly.
Re:What's better about Ruby than Python? - comp.lang.python
by derefr on Friday August 27, 2010 @06:00PM
(#1640433)
The nice thing about code is that (when version controlled) all mistakes can be fixed retroactively. As long as two programmers aren't having a bad day at once, pairing will catch "all" errors. As long as all your programmers aren't having a bad day at once, code review will catch "all" errors again. ;)
Re:What's better about Ruby than Python? - comp.lang.python
by wariola on Friday August 27, 2010 @06:56PM
(#1640572)
This is why you need to automate peer review http://www.parasoft.com
Re:What's better about Ruby than Python? - comp.lang.python
by techiferous on Friday August 27, 2010 @12:55AM
(#1638036)
...and all it takes is one rogue or bad programmer to mess up the code base.