Quality Code of Conduct

I could not find good resources about a code of conduct and would like to start documenting this. The main question I have is really basic things, such as:

  • Someone reports that the “design is broken” when the real problem is that they are using IE6 and have not updated their cache.
  • The team member says that you violated the assembly when in fact they did not get the latest version from the original control.
  • Someone complains that their data is lost when they go to a specific page without explaining how they got there.

I would really like the document that I can give out to clients or team members the next time they complain that "this code sucks", when in fact they have to say: "This code does not fulfill our business goals."

+3
source share
6 answers

This is more like an interpersonal problem, rather than a technical one (with the possible exception of the last point).

If you feel that people are not polite and respectful to each other, there are many solutions (consulting, coaching, etc.), but this should be considered and considered as a social problem, not a technical one.

If this is a simple mistake for part of the complainant, some kind of internal preparation may help. Unfortunately, for this I do not know a good behavior code.

, :

https://developer.mozilla.org/en/Bug_writing_guidelines

http://catb.org/esr/faqs/smart-questions.html

. , .., , - .

+4

, - , , .

, .

' '

" , , .."

, / .

, , .

, , , .

+2

: , :

. .

  • ,
  • ,
  • .

, , ? , . , , .

+1

, , " ", , , .

, "", , , , , . "", ( ), OTOH, , , , , , ).

, , (.. ). , Mozilla, , . QA, , , , , , , .

, .

+1

. , . , , .

. . , , . , , .

, ( " " ), ( " ", " , " ), ( " ", "" ") .., , . , , .

, snarky . , , - . .

, , . . , . , , , .

, , . , , .

+1

-   , , , " " , , : " -".
? ? , , , , , , /​​ , . , / - . , , , .

0

Source: https://habr.com/ru/post/1710154/


All Articles