26

Re: Control of the strong signor

Hello, snaphold, you wrote: S> What correct behavior  in respect of operation control? S> often code the signor is not clear and it seems difficult. The fine bulletproof position 1) not to do operation for the subordinates 2) not to hinder them to work. Allows to live perfectly with subordinates which more silly and more cleverly you. Not clear and complex code it not a problem, a problem if badly structured (I not about indents and arrangement of brackets if that) and kostylno/zaplatnyj. But in this case any it not the signor despite of all studied "technologies".

27

Re: Control of the strong signor

Hello, Qt-Coder, you wrote: S>> it is normal than better the programmer, he is capable to write especially clear code QC> Optionally, level of the abstract thinking can be above. For example, he writes all on templates. Nonsense. The code of good programmers is always clear. If someone "writes all on templates" which very few people understands, most likely or the beginner, or .

28

Re: Control of the strong signor

Hello, snaphold, you wrote: S> What correct behavior  in respect of operation control? S> often code the signor is not clear and it seems difficult. Then it not the signor, and . "Such it is not necessary To us - a disco ". S> the Question: as though you conducted yourselves in a role ? Would talk to it that he wrote so that others understood it. As well told above - that then superfluous, either the signor, or its code, or a command. And generally that developers can be technically more competent, than , quite normally.  be faster the person should good, and competent enough to understand that speak to it.

29

Re: Control of the strong signor

S> the project in itself does not demand difficult things. Tests too are not present. S> people do not know about monads (I for example) and it it is difficult. Let shows on an example in what  with these monads. If cannot show to demand to write so that in a command understood its creation everything, and not just it, the abstruse such.

30

Re: Control of the strong signor

S> the strong programmer (the signor) Comes to the project. S> is stronger  on knowledge. S> the heads  do not change. S> what correct behavior  in respect of operation control? S> often code the signor is not clear and it seems difficult. S> a question: as though you conducted yourselves in a role ? And how  behaves, when orders in the doctor operation to cure it? Too it is dissatisfied, what cannot  the doctor the best knowledge of medicine and deliberates changeover by sillier?