3 ms·
Actually, a machine never accuses you of being the responsible of that error. It usually says "there's an error in the line..." but never addresses it towards t
by namaemuta 10y ago
Actually, a machine never accuses you of being the responsible of that error. It usually says "there's an error in the line..." but never addresses it towards the programmer even though they know that they are the responsible ones of that mistake.
And in fact, that is one of the techniques of conflict management between partners, addressing the problem instead of finding the responsible of it.
- shostack 10y agoSounds like an opportunity for a more opinionated error logging tool... "@Dave, you seem to have made yet another type error on line 56. @jon recently committed code that didn't fail any integration tests. Why can't you be more like @jon?"
- namaemuta 10y agoHmm... I wonder what would be the implications of one with positive reinforcement: "Wow @Dave! that's the smartest code I've ever seen! just one thing, there's a probably-not-that-important error on line 56"
- RodgerTheGreat 10y agoPositive reinforcement which is perceived as insincere will at best have no effect and at worst be seriously insulting. I can't imagine how an automated system which says vaguely positive things about code that it cannot understand would be seen as anything but insincere. If you build a system which successfully encourages actual humans to say nice things about one another's code _and mean it_ while incorporating constructive feedback, it would work beautifully, but that is a markedly more challenging problem...