Pro@programming.dev to Programming@programming.devEnglish · 9 days ago“I noticed a clear violation of our contributing guidelines”github.comexternal-linkmessage-square9fedilinkarrow-up132arrow-down11file-textcross-posted to: [email protected]
arrow-up131arrow-down1external-link“I noticed a clear violation of our contributing guidelines”github.comPro@programming.dev to Programming@programming.devEnglish · 9 days agomessage-square9fedilinkfile-textcross-posted to: [email protected]
minus-squarevalaramech@fedia.iolinkfedilinkarrow-up2·8 days agoIn situations like this, the answer isn’t to argue over the interpretation of the words: it’s to fix the words. If the writers intended “no excessive capitalization or excessive grammatical errors”, then it should be changed to that. If the writers intended “no excessive capitalization and no grammatical errors”, then it should be changed to that. Both situations remove the ambiguity and prevent pedantic internet arguments about language interpretation.
In situations like this, the answer isn’t to argue over the interpretation of the words: it’s to fix the words.
If the writers intended “no excessive capitalization or excessive grammatical errors”, then it should be changed to that.
If the writers intended “no excessive capitalization and no grammatical errors”, then it should be changed to that.
Both situations remove the ambiguity and prevent pedantic internet arguments about language interpretation.