1

Topic: The dead code in the program.

Hello, colleagues. With a companion it is worked over one large-scale project which got to us from the left programmers, accordingly many places should be rewritten. In the project there was a lot of code which at the moment is not used or implements a functional from which has been decided to refuse, I insist that for the further successful operation over the project it is necessary for us to delete all not used code locations, tables, fields, I motivate it with that "idle pieces of the code" simply eat my time for their learning and realization of that they are necessary or not. The colleague refuses it , stating that the given operation "takes away time for search", "takes away time for testing", "suddenly this functional again is required". With its part where it the dead code does not cut at it there are constant problems. I offer jointly  everything, to get rid from superfluous etc. He states that "to rewrite all from zero easier and it is necessary to start to do all anew". To do anew to me it would not be desirable at all since I consider that it will be too long and risks generally are high nothing to make, start to do anew for me similar on "flight from problems" in illusive hope that "well  that we as " though in my opinion code amount absolutely small and by thoughtful operation for a month-other it is possible to put all in order, system modular so it is possible for a part to rewrite on-separateness. In general I realize that my words about "the dead code" it is simple words so started to rummage in a problematics and found a row of the operations confirming that is valid, it is necessary to get rid of the dead code, but here as to "rewritings anew" then at me special experience is not present since I added some projects for other people and in general it was possible to finish these projects to end. "From zero" I was not possible to finish to logical end pair of projects also occasionally watched, as one and  the program is rewritten from zero by three consecutive times, doing one and  operation literally in flow of 4 years.

2

Re: The dead code in the program.

3

Re: The dead code in the program.

Hello, da17, you wrote: D> Hello, colleagues. With a companion it is worked over one large-scale project which got to us from the left programmers, accordingly many places should be rewritten. In the project there was a lot of code which at the moment is not used or implements a functional from which has been decided to refuse, I insist that for the further successful operation over the project it is necessary for us to delete all not used code locations, tables, fields, I motivate it with that "idle pieces of the code" simply eat my time for their learning and realization of that they are necessary or not. The colleague refuses it , stating that the given operation "takes away time for search", "takes away time for testing", "suddenly this functional again is required". With its part where it the dead code does not cut at it there are constant problems. I offer jointly  everything, to get rid from superfluous etc. He states that "to rewrite all from zero easier and it is necessary to start to do all anew". To do anew to me it would not be desirable at all since I consider that it will be too long and risks generally are high nothing to make, start to do anew for me similar on "flight from problems" in illusive hope that "well  that we as " though in my opinion code amount absolutely small and by thoughtful operation for a month-other it is possible to put all in order, system modular so it is possible for a part to rewrite on-separateness. In general I realize that my words about "the dead code" it is simple words so started to rummage in a problematics and found a row of the operations confirming that is valid, it is necessary to get rid of the dead code, but here as to "rewritings anew" then at me special experience is not present since I added some projects for other people and in general it was possible to finish these projects to end. "From zero" I was not possible to finish to logical end pair of projects also occasionally watched, as one and  the program is rewritten from zero by three consecutive times, doing one and  operation literally in flow of 4 years. Give to the colleague a clip. The working code is the code which performs operation and is ready to changes which it is possible to correct. If it is impossible to touch the code, the code does not fulfill the function completely and it is necessary to get rid of it. The less than code, the it is less about it it is necessary to think and the easier it to correct. The careful colleague and then the new code "cuts in a granite" and will cackle round it as a hen-brood hen when it is required to make changes. Such people simply hinder to work. From them one favor: the bad programmer creates two new workplaces in a year. Probably, therefore you also got a job, ha-ha.

4

Re: The dead code in the program.

I on your side. To rewrite only if money there is no place to put and there is a backup plan in case the rewriting fails. It is better to refine the existing code. If and to rewrite, on pieces, carrying out a separate functional in independent units.

5

Re: The dead code in the program.

Hello, Vladek, you wrote: V> From them one favor: the bad programmer creates two new workplaces in a year. Probably, therefore you also got a job, ha-ha. Here it did not understand: he not only creates them, but also occupies too.

6

Re: The dead code in the program.

7

Re: The dead code in the program.

Hello, da17, you wrote: 1) at usage cvs the dead code it is possible safely ; 2) with not used tables and fields I on would be accurater