The programmers who argue for less check-in procedure and automated testing are often the ones who need that the most.
-
-
En réponse à @ChristerEricson
I totally disagree; people who don’t need it are only hurt (productivity) by it w no benefits.
4 réponses 0 Retweet 2 j'aime -
En réponse à @BartWronsk
As a wise man once said, "The needs of the many outweigh the needs of the few." You're expressing an egotistical view.
1 réponse 0 Retweet 0 j'aime -
En réponse à @ChristerEricson
I disagree. From experience:thinner process and more trust (w accountability!) always produces better results of whole team
4 réponses 1 Retweet 0 j'aime -
En réponse à @BartWronsk @ChristerEricson
a good/lean shared test suite helps trust by removing arguments, it introduces objective impersonal parameters
1 réponse 0 Retweet 0 j'aime -
and I'm not a TDD fan at all, but I certainly don't find it harmful to interpersonal trust
1 réponse 0 Retweet 0 j'aime -
En réponse à @ThE_JacO @ChristerEricson
I am not arguing about having or not some tests (I use them daily), just obligatory burdensome checkin procedures
3 réponses 0 Retweet 0 j'aime -
En réponse à @BartWronsk @ThE_JacO
They shouldn't be "burdensome", but they should always be obligatory!
1 réponse 0 Retweet 0 j'aime -
En réponse à @ChristerEricson @BartWronsk
I think the information sharing obtained through a obligatory and reviewed commit process is worth the price.
1 réponse 0 Retweet 2 j'aime
When teams go +10, it's hard to keep in sync: I see mandatory code reviews as a great tool for communication.
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.