There is an old military principle: ... ... Make a piece of work, and do not change anything in someone else's code. What is the meaning of this rule?.
For example, you changed, literally, in a strange bit of code, m. to. noticed a mistake in it ( in your opinion a mistake ). Checked immediately, working. posted the code. And it turns out that the old Murphy's rights. That part of the code that you ... But it turns out that your correct functional smashed in a pile of other places that you did not know.
How can that be then? . Ideally, of course, personally, to come and solve the problem. If not, then ... If changes need to be made urgently, and you can do it yourself, but be sure to have a tracker to the appropriate developer's responsibility to throw a description of the bug with a description of the changes that you made. Request with the developer to check it permissible to do so. For computation of code to the repository must be in the comments indicate the number of your requests in the tracker.
So, if you make a mistake, and your changes are incorrect, then the responsible developer to quickly sort out what's what and will correct. Even if over time it will not happen soon, it 's like your ...
This rule is a corollary: do not change anything in other people's lines of code. Even if it's just a matter of formatting code. Even once ... nothing. If they find out, after which the code was broken commit, it will be seen that this line of code is written for you. Here then will remember and prove: ... ...
...
No comments:
Post a Comment