I would like to know your opinion on whether it is a good idea for developers to put their name or signature on top of each test they write and why (not)?
I would say no. If you really need to know who wrote the test, you should look back in your version control to find out who is to blame. When people begin to put their name on things, you lose the feeling of collective ownership / guilt, and people begin to care more about "their" code, and not about the system as a whole.
, , - , . . , , ? , , ... . Blame .
?
.
, .
, , , , , .)
. , , .
, , , , , , .
, . , , , , ...
, , . , , . , ( ), .
, . , , , , , .
, , , , , ", " " , X ", , , .
, , . , , , , - .
, , . , -, , , , .
, , , . , , .
Source: https://habr.com/ru/post/1704750/More articles:What is X Server and Remote Terminal Server? - terminal-servicesHow to get the value How can I find all the guides in some text? - regexGarbage collection at one object, C # - garbage-collectionThe best way to determine uniqueness and repetition in a text file is command-linePrevent browser from viewing dialog box to resubmit request on update - design-patternsWCF and subclasses - c #Fifth generation languages? - programming-languages | fooobar.comWhy doesn't calling my UPDATE query in an Access database via OleDb work? - c #MS Access, Named Parameters and Column Names - .netAll Articles